I was about to post an answer to a PPCG question when I got this error:

picture of error

It's an LZ-compressed string that reads Hello, World!. I see no reason as to why this character is blocked, as it's just some random Unicode character. Hopefully it's not some emoticon of some illegal cupcake that doesn't show up on my Windows XP machine...

  • Well, no need to attempt to dump raw binary in a post so it is not a general problem. Anyway, the character code is not be the one for a blank square, but instead one that is invalid and only gets displayed as the default Missing Glyph character in this font. – Jongware Sep 13 '15 at 6:15
  • @Jongware When it's code for an esolang, it is a problem. – phase Sep 13 '15 at 6:48
  • 2
    Some characters are banned because they occurred 99.999% in spam only. Your markup is the other 0.001% so is tarred with the same brush. – Robert Longson Sep 13 '15 at 7:01
  • 2
    Why not use hexadecimal, or string literal notation with escape codes? That way you can actually be sure readers of your post can reproduce the value. Posting raw binary data in a post is never helpful. – Martijn Pieters Sep 13 '15 at 7:57
  • 5
    It's almost certainly this bug / feature: meta.stackexchange.com/questions/261609/… – Ilmari Karonen Sep 13 '15 at 8:01
  • And as @Martijn notes, the standard work-around is to post a hex / base64 dump of your code instead. – Ilmari Karonen Sep 13 '15 at 8:05
  • As you seem to want it on a a line by itself anyway (did you type two spaces after that first line?): what if you add a blank line and then format as code by indenting with 4 spaces, instead of manually doing <pre>? – Arjan Sep 13 '15 at 9:41