It appears that now you can no longer just put spaces at the end of text to get past the character limit. You can still put them in the middle, where they get truncated to a single space.

I always thought that being able to use spaces to get past the minimum character limit was one of the best hidden-features of the S[OFU] sites.

Please vote to get this reimplemented.

  • 6
    They're not truncated - they still show up in the source - but browsers always render multiple spaces as one space. Sep 26, 2009 at 16:50
  • QQ more Sep 26, 2009 at 18:28
  • That doesn't help when I want to comment "Yes" !!!
    – badp
    Dec 7, 2009 at 15:06

2 Answers 2


when doing length check, switched to .RemoveExtraSpaces() on the server side instead of .Trim()

  • 2
    Was it really a problem?
    – perbert
    Sep 26, 2009 at 23:38
  • 8
    it wasn't really a problem; I didn't care either way. But the weekly opening of "bugs" from ZOMG HAXOR programmers discovering the same boring trick was too much for me to take. So, we fixed the "bug". Sep 27, 2009 at 1:19
  • 1
    ␠␠␠␠␠␠␠␠␠␠␠␠␠␠␠ Sep 28, 2009 at 2:31

As long as the character limit exists, and it seems that it will, it makes sense for it to be enforced. 15 characters isn't a whole lot, really. Can anyone come up with a good example where it's not possible to expand the thought to meet the quota?

  • How did you do that Kyle??
    – deleted
    Sep 26, 2009 at 18:19
  • 3
    I can't answer tour question with NO because it's not 15 characters thus forcing me to type more... #fail
    – RSolberg
    Sep 26, 2009 at 18:26
  • Not tour rather your....
    – RSolberg
    Sep 26, 2009 at 18:27
  • 3
    @Isaac: fretje is correct, just put a bunch of spaces between backquotes. but don't tell anyone. Sep 26, 2009 at 19:03

You must log in to answer this question.

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