I had this idea about two years ago! https://github.com/keith-turner/ecoji … But after Base65536, Base32768, HexagramEncode, BrailleEncode and Base1 I had run out of steam
-
Show this thread
-
Ecoji has an efficiency of 31.25% - each byte of input becomes 3.2 bytes of output, regardless of whether the output is encoded as UTF-8, UTF-16 or UTF-32. Compare Base64 (optimal for UTF-8, 75% efficient), Base32768 (UTF-16, 93.75%) or Base65536 (UTF-32, 50%)
2 replies 1 retweet 0 likesShow this thread -
Replying to @SimonSapin
In theory, but it uses a large number of symbols and punctuation characters which I consider to be unsafe
2:37 PM - 18 Mar 2018
0 replies
0 retweets
0 likes
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.