quarantine 'em

I de-obfuscated a bunch of client code (tedious) and came to the same conclusion as people have reached via experimentation...

The new maximum Tweet length is 280 (normalized) Unicode characters, EXCEPT THAT characters 0x1100 upwards all count double.

"Unicode characters 0x100 upwards" includes every character used for Base65536, including the padding characters.

So the maximum number of Base65536 characters allowed in a Tweet remains 140, and the maximum amount of data so expressed remains 280 bytes.

(As far as I know, this limit is only enforced client-side. It is possible to circumvent the check and send 280 characters/560 bytes...

...but I'm taking the check seriously for the purposes of this piece of work.)

So, no, the new changes do not make it possible to send 560 bytes of text per Tweet. That limit stays at 280 bytes. With current encodings.

Twitter has divided Unicode up into two sets for our purposes: "good" (0x0000 to 0x10FF, weight 1) and "bad" (0x1100 to 0x10FFFF, weight 2).