What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 131 Stack Exchange communities.

I don't know what the reviewers were thinking, but this is not the issue here:

Enter image description here

Rather, the limit was circumvented by inserting six U+200B (UTF-8 E2 80 8B, "ZERO WIDTH SPACE") at the end of the sample code:

Enter image description here

Should this be added to what is considered white space in the edit length restriction? Or does the old policy still apply?

share|improve this question
This​​​​​​​​​​​​​​​​​​ –  Peter Mortensen Mar 5 at 21:01
also​​​​​​​​​​​​​​​​​​ –  Peter Mortensen Mar 5 at 21:03
works​​​​​​​​​​​​​​​​​​ –  Peter Mortensen Mar 5 at 21:03
in​​​​​​​​​​​​​​​​​​ –  Peter Mortensen Mar 5 at 21:03
comments​​​​​​​​​​​​​​​​​​ –  Peter Mortensen Mar 5 at 21:04
!​​​​​​​​​​​​​​​​​​ –  Peter Mortensen Mar 5 at 21:04
One of the reviewers was the answerer BTW. Presumably the correction from 11 to 10 and additional colon was technically correct. –  Martin Smith Mar 5 at 21:05
@MartinSmith It was reverted an hour later –  gunr2171 Mar 5 at 21:06
@gunr2171 Oh yes. Strange! –  Martin Smith Mar 5 at 21:07
I've seen many attempts to circumvent the six-character minimum, but this is a new one. (I'm also tempted to tear the editor a new one.) –  michaelb958 Mar 5 at 21:10
It's one thing to use the zero width space in comments. But it's another to use it in edits to get around the 6-character minimum... –  Mysticial Mar 5 at 21:22
Alternate suggestion: Automatic moderator flag for suggested edits that are shorter than the length restriction after stripping out ZWSPs. :D:D:D –  Mysticial Mar 5 at 21:32
Unless there are many examples of abuse, there's little reason to act. There are lots of ways to overcome the built in rules checker, but it's generally only necessary to strengthen rules when abuse is widespread and very detrimental. Otherwise you're going to spend significant development time making the rules checking huge and obese for very little return on your time investment. Not only that, but the rules checker will run that much slower with each addition. You'll need to add many, many more examples of such abuse before it's worth acting on. –  Adam Davis Mar 5 at 21:39
With Unicode being vast, there are many to choose from, but if it is in some kind of table it might be feasible. –  Peter Mortensen Mar 5 at 21:40
I'm sorry, but what is the point of doing this? They'll just end up resorting to other, uglier ways to circumvent the limit. –  NullUserException อ_อ Mar 5 at 22:29

1 Answer 1

I don't see any need for this.

Anyone using this kind of hack has probably evaluated trying to bring the edit up to 6 characters by more conventional means first and concluded that there aren't 6 such edits to be made.

I can't gauge the technical accuracy of this specific edit myself but, assuming that the missing colon was correctly added, it is difficult to see what other 5 changes they could have made to this 100% code answer.

The real purpose of this restriction is to ensure that editors fix everything in the post.

A much less exotic workaround they could also have used (apparently) is simply adding  .

share|improve this answer
The difference is that you actually see  , because it isn't zero-width. And there's no promise the user has tried to bring anything up to 6 characters: already knowing this trick, they could just say "I'll correct that, then insert a bunch of zero width spaces." –  doppelgreener Mar 5 at 22:45
@JonathanHobbs - Why is seeing   a benefit? It is just noise. If people try and abuse this trick and use it when there are clear other things they could have edited I would fully expect a rejection for "too minor". –  Martin Smith Mar 5 at 22:50
Actually, fair point on the 'too minor'. Seeing   is a benefit because you understand what they're doing to somehow beat the 6 character thing. –  doppelgreener Mar 5 at 22:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .