And there it is. Base65536 (280 bytes per Tweet) is now officially obsoleted by Base2048 (385 bytes per Tweet)https://github.com/qntm/base2048
Show this thread
To efficiently transmit binary data as * UTF-8: use Base64 or Base85 * UTF-16: use Base32768 https://github.com/qntm/base32768 * UTF-32: use Base65536 https://github.com/qntm/base65536 * Tweets: use Base2048https://github.com/qntm/base2048
-
-
COINCIDENTALLY, here's my essay "What makes a Unicode code point safe?" https://qntm.org/safe
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.