We can get around the six-character limitation with the strategic deployment of HTML character-entities - including, but perhaps not limited to, and ­.
NOTE: ­ is a soft-hypen; it will render if the enclosing text can span a line-break.
NOTE: This technique does not work in topic titles, which render the entities as plain-text. See QUEST for ALL CAPS TOPIC TITLES for more.
There are some other entities that might be worth exploring:
emsp em space
thinsp thin space
zwnj zero-width non-joiner
zwj zero-width joiner
lrm left-to-right mark
rlm right-to-left mark```
It may be an old think, but I figured it out on my own when Bgaji couldn’t post Bof. I remember running into the barrier myself, and thought about the trick – which I regularly use to get empty paragraphs for extra “time/space” padding in a post.
Eventually, I wondered what would happen if NOTHING but was the body of the post… YEP! The algorithm checks the character-count of the post source, not the character-count of the post render.
I’m curious what the images are–are they of any significance, or just something random because it was not allowed to be left blank? (On my screen, the profile image looks like a gold/white plaid or grid/table of some sort; the header image seems like a map of some sort…both very faint but can be seen better if the screen is tilted enough.) Care to tell?
