alt Hacker News> Here’s the alphabet, in encoding order:
> ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789!#$%&'()+,-;=@[]^_`{}~
Yeah I definitely don't want any of those last ~22 characters in file names if I need to do anything with them from a shell
Replies
dgacmu • today at 2:42 PM
Yeah, I'm sympathetic to their desire for compression and efficiency but base64URL is way more shell-friendly.
I quite like base58 for human-presented identifiers also. I tend to use it instead of hex for having ~8-16 character IDs of things.
➕ show 1 reply
Dwedit • today at 2:50 PM
Even just "-" in a filename is problematic, since you can name actual files with "--" at the beginning, and the name could match a switch.
➕ show 1 reply
brookst • today at 2:33 PM
What you don’t want a file named `reboot`?
Moreover, I'd be nervous about the fact that filenames on Windows tend to be case insensitive.