|
|
Alas, I just lost a post on this topic, and addressing your comment above, XK.
However, I'm not entirely sure where one goes with this - the last time Hieronymus started a thread, very like this one in fact, in Policy it was a result of his behaviour here, and after the first post he never returned to it. So, I'm not sure whether this thread is intended to be a discussion, or simply a sort of venting of steam.
This latest incident originates in Nico's threadrot of "Ratatouille", culminating in this post, where ze has been goaded into saying something somewhat ontopic, but has surrounded it with trollery, here. This Policy thread was started after Hieronymus got involved with this contribution, here, not actually talking about Ratatouille at all.
Also in this thread we find an immediate and useful answer, when Gourami, Decadent Nightfalling and I all ignore Hieronymus' abusive tone and content, and instead focus on the actual, thread-relevant content that preceded it - content generated by myself that he referenced only by saying:
While the attempt to bring more content to the table is appreciated, it's blown to smithereens by your sniping first paragraph.
Apparently it was not. So, essentially, the best answer to the question:
How can a moderator best keep a thread from unravelling into threadrot, especially the stripe of threadrot that is a conflict between members within the thread?
Is, in this case, "don't flame". Failing that, the second answer is "ignore flames". The first we did not manage, the second we largely did, presumably hence this thread. If neither of those works, I think one might have to start acting as a moderator, which may involve acknowledging and accepting responsibility for any part one might have played in the run-up to the disruption - recusing one's previous involvement, in effect - or acknowledging one's personal unsuitability to peacemake, and asking a friend, depending on whether or not one has succumbed to the temptation to throw the odd punch oneself. |
|
|