Anyone got any information on how the text rendering bug actually works (not just hand-waving it away as "oh it's UTF-8")?
I can see that the file alternates between segments of:
- Repetitions of the glyph "t̴́̍̒", which is a lowercase t with a combining tilde overlay, an acute accent, a vertical line above, and a turned comma above
- Random-looking ASCII characters with lots of apostrophes (spelled as ' in the HTML)
- Short sequences of spaces, non-breaking spaces, and zero-width joiners
- Occasional emoji
The "t̴́̍̒"s manage to slow down my terminal and glitch its rendering a bit. Is it that they're unexpectedly tall? But we've had zalgo-text for a while and it hasn't actually crashed devices.
I can see that the file alternates between segments of:
- Repetitions of the glyph "t̴́̍̒", which is a lowercase t with a combining tilde overlay, an acute accent, a vertical line above, and a turned comma above
- Random-looking ASCII characters with lots of apostrophes (spelled as ' in the HTML)
- Short sequences of spaces, non-breaking spaces, and zero-width joiners
- Occasional emoji
The "t̴́̍̒"s manage to slow down my terminal and glitch its rendering a bit. Is it that they're unexpectedly tall? But we've had zalgo-text for a while and it hasn't actually crashed devices.