Apparently, somebody set up us the BOM.
Apparently all YouTube comments have a UTF-8 BOM... at the end. YouTube, don't drink and webdev. @FakeUnicodepic.twitter.com/QSnzPdNhti
-
-
- Show replies
New conversation -
-
-
Is this the Unicode equivalent of "while(1);" ?
- Show replies
New conversation -
-
-
-
BOM is very important to UTF-8, but mostly in unambiguously identifying a file as NOT being UTF-8.
#NeverFFEForget [Although there are *rare* cases where you can't easily specify an encoding, like remotely hosted css/js files, and a UTF-8 BOM will correctly identify it.] - Show replies
New conversation -
-
-
I immediately thought, it's the start of the next frame BOM in the TCP stream, before it's encapsulated in XML/HTTP Don't we love off-by-one errors
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This BOM was inserted there by their AI algorithm because it decided it'd increase $$$ and user engagement.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It’s not a BOM - it’s a ZWNBSP. It’s a valid character and only a BOM if it’s at the beginning. As the actual bytes. It certainly is never a BOM if & encoded or encoded in any other form than the bytes defined as BOM.
-
U+FEFF is deprecated in favor of U+2060 when not a BOM. It is not &-encoded; that's Chrome being useful and making it explicit in the dev tools. The character comes back as a UTF-8 BOM (EF BB BF) in the JSON request for the comments. It's a BOM, in a stupid place.pic.twitter.com/jj0YXmRu4k
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.