Looking at an answer that was "bumped" by a recent edit, I saw that a user with full editing privileges attempted to work around the 30 character minimum by adding the following text:
Body must be at least 30 characters
What a horrible edit! We would be better off just having the short, likely low-quality answer than adding in noise like this. So I removed this line and added in some additional text to lengthen the answer. You can see the full revision history here.
Then I started looking at that user's edit history, and I found that this isn't the first time he's done this. Within the past 2 days, I found the following edits:
- How do I extract xml properties using shell scripts?
- How do I write non ascii chars using echo?
- How do you call those little annoying cases you have to check all the time?
- How do you call those little annoying cases you have to check all the time?
- Lightweight and portable regex library for C/C++?
- Best lightweight web server (only static content) for windows
- Capturing Groups From a Grep RegEx
Obviously I could go through and edit them out, but that doesn't stop the problem from occurring. There are several issues that spring immediately to mind:
How do we stop this particular user from doing this? And more generally, how do we stop any user who is trusted with full editing privileges from continuing to make obviously bad edits?
I could leave a non-authoritative comment using the @-reply system to inform him, but this just adds even more noise to someone else's post (and their inbox). It also may not persuade him, since I don't have one of those diamond thingies after my user name.
Or I could flag one of the edits for a moderator's attention, describe the problem as I have here, and ask one of them to deal with it.
If we're going to enforce character minimums for posts (which, by the way, I think is a fantastic idea), then we need to make it more difficult to trivially work around. We already seem to ignore characters inside of HTML comments, but maybe we also need to block self-referential mentions of the 30 character minimum.
I'm not actually sure if this is possible, though. If not, we might need to reconsider ignoring HTML comments. That's how people used to work around the minimum length, and it seems to me like it was preferable to adding noise that appears in the body of the post itself.
Why is this user finding these old posts and making these edits in the first place? He's not changing anything else, so he's not hitting the character minimum when he goes to submit an edit. I suppose he's finding them using one of the Review pages. If that's the case, we seriously need to improve the Review interface. There needs to be an obvious way to indicate that a post is OK and make it disappear from the Review page without forcing a useless edit.