Related but opposite, a tool I made a couple of years ago.<p><a href="https://github.com/ctsrc/Base256" rel="nofollow">https://github.com/ctsrc/Base256</a><p>> Encode and decode data in base 256<p>> […]<p>> You might expect data encoded in base 256 to be more space efficient than data encoded in base 16, but with this particular set of symbols, that is not the case! Likewise, you have to type more, not less, than you would if you use my base 256 instead of base 16. So why?<p>> The purpose […] is to make manual input of binary data onto a computer less error-prone compared to typing in the base 16 or base 64 encoding of said data. Whereas manually typing out base 64 is painful, and base 16 makes it easy to lose track of where you are while typing, [this program] attempts to remedy both of these problems by using 256 different words from the EFF autocomplete-friendly wordlist.<p>Disclaimer: I am not using this base 256 program myself, even though I authored it. It just serves as a fun little experiment.