I’m certain that @waetherman was also wanting to make damn sure we didn’t ban anyone/further enflame the situation around those circumstances, rather wanting to avoid them instead. That aim I also heartily agree with as well.
Not that I know of. However, I know that new feature requests are a thing, and can think of at least two ways of bodging it in in the meantime:
If we can get a MAILTO: into a topic post or topic Wiki HTML, then we can receive a fairly automated email from the user’s registered email, and flag it very clearly in a standard format for the ban reason. (If Discourse can’t do this, a link to a specific page on whatever CMS our articles-front-page ends up being - maybe direct triggering a mailto there?)
Or, just accept an email to BANMEFORADAYPLEASE@happymutantemail.cx from registered emails, a là automated unsubscription from mailing lists.
Part or all of the handling of the auto email may even be scriptable outside of Discourse.
But I’d certainly suggest requesting the feature. I can only think of one BBS that I know of where a self-ban hasn’t been requested (that I know of), so it’d be a common-use addition.
In some ways, those types of statements kind of strike me along the same lines as the “I know you’ll just delete my post for saying so, but…” ones. The statement by itself shouldn’t be cause for the action, because if the person actually has a valid point then taking the action is just going to make things worse. Circumstances definitely matter, of course, but I’d feel the action should have supporting cause in that kind of case.
I really don’t understand the whole requests to be banned trend but that doesn’t mean it is a valid need of some people. I guess. I’m trying to be nice…
Now this I like. Put the user in control. Give them to tools to take them self out of the conversation when they get too heated. A site wide time out would be nice as mentioned. Also a hide this thread from me would allow them to continue participating here if it’s just one thread that is the problem.
The notification status options for each thread go so far in that direction, with thread muting - hiding the fact that the thread has been updated in multiple ways, including updated and latest lists unless you actually go look.
You can still go find it under its category, of course.
And promoting them - I was hoping I wasn’t just explaining something you already knew, mind.
Maybe a ‘So you’re really steamed about this topic’ page in the user help (or other html page, so it can be pointed-to by people), detailing flagging, and complaining to mods, but also topic muting and even the time-out, if it can be implementable. Would need phrasing carefully though.
Just good old Attention Management - we learn the useful subset of options, and then filter thereafter. The perils of using meat-that-thinks to, well, think with.
I think I have a jQuery plugin for that … or at least, I sometimes wish I did! It would certainly make users pay more attention to my validation messages.
About moderation guidelines: do the moderators have an agreed-upon grid or table of bans and suspensions determined by frequency, volume and severity? I’ve seen instances at another BBS where a moderator gives one user a medium-length suspension, and another moderator extends the suspension to the middle of the next decade. What is the likelihood of that happening here? When a moderator takes action, does she take it independently and the other moderators accept it without question, or is it possible that another moderator would think “nah, three months is much too light. This needs to be eight years or longer.”
Judge One: “Deary me. You stole a car. First offense. Three months in jail for you.”
Judge Two: “WTF dude?! The user STOLE A CAR! OFF WITH HIS HEAD!!”