News for hackers. Stuff that matters.
Re:Base65536 – Unicode's answer to Base64 by desdiv on Saturday December 05, 2015 @08:54PM (#10684049)
Unfortunately that won't work. Twitter doesn't support the full Unicode; they strip out any Unicode code points that's not used by "normal" people.
Re:Base65536 – Unicode's answer to Base64 by simplicio on Saturday December 05, 2015 @09:31PM (#10684132)
Are you sure? I just posted a tweet in Cuneiform, which is outside the BMP. So their view of "normal people" seems to encompass ancient Sumerians, at least.
Re:Base65536 – Unicode's answer to Base64 by mikeash on Saturday December 05, 2015 @09:02PM (#10684072)
Interesting, is there a list of what they strip out? I know they apply normalization so that would eliminate a few, but I think that wouldn't do too much on its own.
Re:Base65536 – Unicode's answer to Base64 by TazeTSchnitzel on Saturday December 05, 2015 @09:00PM (#10684063)
> they strip out any Unicode code points that's not used by "normal" people.

Such as?

Re:Base65536 – Unicode's answer to Base64 by goodplay on Saturday December 05, 2015 @09:36PM (#10684143)
LTR and RTL marks (all of them), which are used when the default Unicode bidi algorithm fails to display two intertwined scripts correctly. They are especially useful when writing short technical tweets.

I bet normal people would use them too if they knew about them and were given a chance, but normal people can't because twitter doesn't allow codepoints that aren't used by normal people.

Re:Base65536 – Unicode's answer to Base64 by TazeTSchnitzel on Saturday December 05, 2015 @09:48PM (#10684165)
Stripping out LTR and RTL override might be reasonable because they're frequently abused to screw up website layouts. But stripping all of the marks is just discrimination against people who need to write bi-directional text.
Re:Base65536 – Unicode's answer to Base64 by cbd1984 on Saturday December 05, 2015 @11:25PM (#10684402)
> Stripping out LTR and RTL override might be reasonable because they're frequently abused to screw up website layouts.

As long as Twitter allows Zalgo it isn't that concerned about website layouts.

(Zalgo: Rampant abuse of stacking combining diacritical marks above and below the line. It can get really, really... uh... impressive, in a Lovecraftian typewriter art kind of way.)

Re:Base65536 – Unicode's answer to Base64 by goodplay on Sunday December 06, 2015 @02:52AM (#10684691)
The issue of effecting web layout can be resolved by simply appending the appropriate resetting codepoint to the tweets. (U+202C for bidi overrides)
Re:Base65536 – Unicode's answer to Base64 by amptorn on Sunday December 06, 2015 @05:07AM (#10684847)
Well, null, to start with. Other ASCII control characters. Consecutive line breaks, too.