Hidden space - a hole in the MN time/space continuum?

01101000 01100001 01110010 00100000 01100100 01100101 00100000 01101000 01100001 01110010

!

Fuck me. It is like a Bloke Nerd Breeding Sanctuary now.

"Finally, someone to talk binary to..." has to go on your tombstone I feel.

For those wondering, I used ASCII to Binary / Binary to ASCII on TheSkull.com to translate the phrase to binary.

Trust me to get it wrong.

Or in our language:
01010100011100100111010101110011011101000010000001101101011001010010000001110100
0110111 1001000000110011101100101011101000010000001101001011101000010000001110111
0111001001101111011011100 110011100101110
(without any CR/LF the browser decides to display in that binary sequence)

@nannynick, finally someone to talk binary to, except CRLF would be 00001101 00001010, I see what you did though, you split the two bytes into four half bytes and then interpreted each digit into each half byte. What you've said would be hex 8, hex 11 which is backspace and a "vertical tab".

So that's CRLF is 0001 0000 0001 0011 I think.

what bastian said

look V wilf - a shiney penny

where... where...

The Hex 10 and the Hex 13 are CRLF or Carriage Return and Line Feed which what people have been referring to as the "hard return". No black magic sorry.

Oh look: a shiny thing over there...

wow i have a busy day and you lot have solve the problem and constructed the solution. Does big tech need to come back now? I still say that should they let mn loose on the world it would solve the world crisis .

There are hexes too? It is way beyond me. The rouge spaces are on my shamed cheeks:

@Deadworm, the rouge spaces are infact two characters when viewing them from the "view source", a hex 10 and a hex 13. They don't count in to 100 as they're the sentinel character sequence (or termintator) indicating an end of line for word wrapping. The s are being added after the line wrapping is being done, you can tell this because the rows with s in them have a number of characters more which are a whole number multiple of the number of s in that line.

Dammit

@nannynick, the sad emoticon (when the square brackets are added) is five characters which 100 is a whole number of, biscuit on the other hand (with the ]s) is 8 characters which doesn't divide into 100 nicely.

There is a forced LFCR (new line) between your sad faces but is easier to miss than the forced LFCR on your row of biscuits.

The problem is due to the order of operation of formatting the text in posts. What I would expect to happen is that the content is saved to the database in the rawest format possible (as typed but cleansed etc), it would then be the responsibility of the code to handle the text to display it to ensure the formatting is as desired.

The obvious solution would be to wrap after replacing the emoticons with images (this would be my recommended approach, but then who am I)

Just
when
I
was
going
to
go
to
bed
for
the
night
I
came
in
here
and
fell
into
a
black
hole,
now
did
it
work?

Are these The Rules?

If you don't use any hard returns the site usually relies on spacebar-imposed spaces to generate line breaks.

If you don't use the spacebar, the site imposes a line break after every 100 unspaced characters.

If you have not used any hard returns then this rule will result in a neat block of 100-character-wide text.

If you have used hard returns, then the code that the site has used to enforce the linebreak is superfluous since the text will break where you have told it to. But that coding still generates a space, which will appear in a manner that is apparently random but is in fact dictated by the 100-character rule.

It doesn?t look like it is gernerated every 100 charaters because the space itself counts as 4 invisible characters (i.e. the characters ??)

I fall through the gaps all the time
000000000000000000000000000000000000000000001
000000000000000000000000000000000000000000001
0000 00000000000000000000000000000000000000001
000000000000000000000000000000000000000000001
0000000000 00000000000000000000000000000000001
000000000000000000000000000000000000000000001
0000000000000000 00000000000000000000000000001
000000000000000000000000000000000000000000001
0000000000000000000000 00000000000000000000001
000000000000000000000000000000000000000000001
0000000000000000000000000000 00000000000000001
000000000000000000000000000000000000000000001

Ineedacleaner keeps falling in the gaps doesn't appear to be pressing return before the end of line, but letting the text run and run.

There just aren't enough biscuit emoticons in the world, sometimes.

oops, that meant why doesn't Ineedacleaner get any spaces?! Mysterious 'not' got added

this is very strange... I kinda understand the explanations about the wrapping code thingy but WHY doesn't Ineedacleaner not get any spaces?!

Exactly. Back away now while you still can imagine you're on X Files

sniff