« first day (4301 days earlier)      last day (242 days later) » 

01:49
@BeastOfCaerbannog Looks like the sequence was a flag on an unusual comment with an emoji that broke the comment display. The comment was removed and then a lock placed. Loks like it is no longer needed so I have removed it...
 
3 hours later…
04:54
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Ubuntu Pro tab in Ubuntu 23.04‭ by LainerD‭ on askubuntu.com
Autoflagging disabled until restart
05:35
@andrew.46 I yes! I remember now! I'm the one that had flagged that comment. I had also mentioned that I had flagged it is to the user that had posted it here: chat.stackexchange.com/transcript/3877?m=64550847#64550847
However, I don't think that locking the post for this, not even with a timeout but indefinitely, was the right action. It was just a comment that came from an established user that was also active in moderation and frequent in this room. It was just a bad comment that was flagged and deleting it should have been enough.
Locking the post indefinitely is an extreme measure for such a case and not required at all. It's an unneeded authoritative escalation that came again by a mod who often overuses their mod power to state authority in situations which can be solved in other ways or have even already been solved. I don't like this behavior.
@BeastOfCaerbannog I do not like to second guess the decisions of other Mods, particularly when they are much more experienced than myself. However I also have no problems altering such decisions when there is a subsequent need, as in this case :)
@BeastOfCaerbannog Reopened
06:05
@andrew.46 yes, I understand your position. Thanks for unlocking the post!
@andrew.46 thank you!
06:30
Locking is a funny thing and @Zanna may have some thoughts as well. I use it in a time limited manner if there is a dispute in the comments that is becoming too heated and less and less about the question at hand. I also use it if a question or answer is being further discussed on Meta and needs to stay as is for a period while under discussion. Also for posts that should not normally be edited: the only example I have at the moment is the 'in-memoriam' post on Meta.
2
But most commonly to defuse heated discussions :)
2
 
1 hour later…
07:34
@andrew.46 I certainly agree with locking posts for these reasons and usually locking them for a limited time should be enough (except of course for specific cases where the subject of a post is guaranteed to cause a heated debate). But actions such as locking posts, suspending users, escalating to CMs, or even deleting comments in many cases shouldn't be the only way of deescalation.
Even when such things are required, they should be explained and justified (I appreciate that you always do that), and not be applied in an authoritative way.
@andrew.46 I posted an answer and flagged comments below the question for deletion.
 
1 hour later…
08:50
@BeastOfCaerbannog It is all looking very good now :)
@andrew.46 :)
09:37
[ SmokeDetector | MS ] Url-only title, bad ip for hostname in body, blacklisted website in body, link at beginning of body, pattern-matching website in body, +3 more (438): www.eventbrite.com/e/zencortextm-listen-with-confidence-the-power-of-hearing-support-tickets-876499883747‭ by foathyst ephensx‭ on askubuntu.com
 
2 hours later…
 
1 hour later…
13:57
[ SmokeDetector | MS ] Link at end of answer (62): IntelliJ crashing since latest update‭ by sampleNull‭ on askubuntu.com
14:44
[ SmokeDetector | MS ] Link at beginning of body (44): Ubuntu MATE 23.04 Lunar Lobster for amd64 systems‭ by BrowHarddude‭ on askubuntu.com
 
1 hour later…
 
2 hours later…
 
1 hour later…
19:32
@natty feedback askubuntu.com/a/1509430 tp
@natty feedback askubuntu.com/a/1509363 tp
@natty feedback askubuntu.com/a/1509357 tp
 
2 hours later…
22:03
@natty feedback askubuntu.com/a/1509262 tp
@natty feedback askubuntu.com/a/1509216 tp
Error in arguments passed

« first day (4301 days earlier)      last day (242 days later) »