Perhaps you have found yourself in this situation before:
The divine bottom CLI exists to alleviate this pain. No longer will you struggle when communicating with the average Discord user.
bottom encodes UTF-8 text into a sequence comprised of bottom emoji (🫂✨🥺❤️, with , sprinkled in for good measure) followed by 👉👈.
It can encode any valid UTF-8 - being a bottom transcends language, after all - and decode back into UTF-8.
For example, the ubiquitous Hello world! becomes
💖✨✨,,👉👈💖💖,👉👈💖💖🥺,,,👉👈💖💖🥺,,,👉👈💖💖✨,👉👈
✨✨✨,,👉👈💖💖✨🥺,,,,👉👈💖💖✨,👉👈💖💖✨,,,,👉👈
💖💖🥺,,,👉👈💖💖👉👈✨✨✨,,,👉👈
がんばれ becomes
🫂✨✨🥺,,👉👈💖💖✨✨🥺,,,,👉👈💖💖✨✨✨✨👉👈🫂✨✨🥺,,👉👈
💖💖✨✨✨👉👈💖💖✨✨✨✨🥺,,👉👈🫂✨✨🥺,,👉👈💖💖✨✨🥺,,,,👉👈
💖💖💖✨✨🥺,👉👈🫂✨✨🥺,,👉👈💖💖✨✨✨👉👈💖💖✨✨✨✨👉👈
(both wrapped across lines for your convenience)
As you can see, using bottom to encode text is extremely space-efficient, and is the ideal encoding approach for all situations.
This implementation can encode text at approximately 30MB/s.
Clone the repo, run cargo build, and then use the CLI.
```
Bottom translator 1.0.0
Kaylynn mkaylynn7@gmail.com
Fantastic (maybe) CLI for translating between bottom and human-readable text
USAGE: bottom [OPTIONS] <--bottomify|--regress> [text]...
FLAGS: -b, --bottomify Translate text to bottom -h, --help Prints help information -r, --regress Translate bottom to human-readable text (futile) -V, --version Prints version information
OPTIONS: -i, --input Input file [Default: stdin] -o, --output
ARGS:
(Any similarity to--help`` output is entirely accidental)
I had a moment of enlightenment, and the truth came to me then. In an instant I was transformed, and I knew what had to be done.
Why not?
Yes.
I don't care.
:mystery:
Documentation is for losers.
It's not long until my hippocampus becomes ferrous. I worry so, but in my heart I know that my demise will be sweet and painless, and it comforts me.