Encode things into Emoji.
Base💯 can represent any byte with a unique emoji symbol, therefore it can represent binary data with zero printable overhead (see caveats for more info).
$ echo "the quick brown fox jumped over the lazy dog" | base100
👫👟👜🐗👨👬👠👚👢🐗👙👩👦👮👥🐗👝👦👯🐗👡👬👤👧👜👛🐗👦👭👜👩🐗👫👟👜🐗👣👘👱👰🐗👛👦👞🐁
Base💯 will read from stdin unless a file is specified, will write UTF-8 to
stdout, and has a similar API to GNU's base64. Data is encoded by default,
unless --decode is specified; the --encode flag does nothing and exists
solely to accommodate lazy people who don't want to read the docs (like me).
``` USAGE: base100 [FLAGS] [input]
FLAGS: -d, --decode Tells base💯 to decode this data -e, --encode Tells base💯 to encode this data -h, --help Prints help information -V, --version Prints version information
ARGS: The input file to use ```
Base💯 is very space inefficient. It bloats the size of your data by around 3x, and should only be used if you have to display encoded binary data in as few printable characters as possible. It is, however, very suitable for human interaction. Encoded hashes and checksums become very easy to verify at a glance, and take up much less space on a terminal.
``` $ base100 --version base💯 0.3.0
$ base64 --version base64 (GNU coreutils) 8.28
$ cat /dev/urandom | pv | base100 > /dev/null [ 247MiB/s]
$ cat /dev/urandom | pv | base64 > /dev/null [ 232MiB/s]
$ cat /dev/urandom | pv | base100 | base100 -d > /dev/null [ 233MiB/s]
$ cat /dev/urandom | pv | base64 | base64 -d > /dev/null [ 176MiB/s] ```
In both scenarios, base💯 compares favorably to GNU base64.