You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
And there it is. Base65536 (280 bytes per Tweet) is now officially obsoleted by Base2048 (385 bytes per Tweet)https://github.com/qntm/base2048
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
Is "WITH" a real license?
Have I left in a typo?
Hmm. I presume you've tried, but it's theoretically possible to pack more in using some heavy codepoints, but less often... though I don't think you can even come close to cracking the next power of 2...
... just ran the numbers, using every safe char gives a theoretical max of 11.22*280 bits per tweet, up from 11.19*280 from just the 2343 light chars. Seems hardly worth the effort.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
