While you are correct in that this is not a situation where revisions should be erased, you are incorrect in that mods can redact revisions as of recent changes. It takes two mods: one to propose the redaction, and another to approve it.

superuser.com/home/recommended/debug

@Twisty In short: Simply tag it, and if it gets good answers, it will be retagged into a community-faq. For more info, see the tag wiki: superuser.com/tags/community-faq-proposed/info. With that being said, you should probably raise a meta question too in order to get a consensus toward creating one and to get attention to it once it's created.

@Ramhound Yeah, the reason they removed it was because it was being abused (only in 50% of cases was it used correctly).

@Ramhound That's true. (Except in certain cases, when a close reason is removed, it doesn't mean the questions are now on-topic. The custom-comment off-topic close reason exists to cover topics previously covered by boilerplate close reasons. Example: the "bugs in beta software and prototype hardware" close reason was removed, but questions about those are still to be closed.)

This already exists in the Low Quality Posts review queue, for answers.

Given that Travel.SE is doing the same thing I think it's a good idea.

Don't forget community-faq-proposed either!

@nhinkle Just tried it. Even though the little bar at the bottom says that there are enough characters, once the comment is submitted, the character check is rerun again after stripping, and if the text after stripping is less than 15 characters, you'll get an error.

Another moderator (as in community moderator) posted an answer here. Don't remember who, as I can't find the original answer.

Is there any recourse in case you do happen to get banned from an incident like this?

This can't be used to bypass the character requirement, right?

There is a technical difference. Spam flags feed into the spam filters, while offensive flags don't.