Hacker News new | ask | show | jobs
by bajsejohannes 996 days ago
I'm actually working on encrypting database keys like this, and I opted for a string ID with "url safe" base64. It avoids the ambiguity of looking like a UUID when it's not, and I prefer "o3Ru98R3Qw-_x2MdiEEdSQ" in a URL over "a3746ef7-c477-430f-bfc7-631d88411d49". (Not that either one is very beautiful)
1 comments

Curious on the preference there, especially when characters in base64url encoding can look similar/ambiguous in some fonts.
The preference is purely about the amount of characters. I hope no one will ever actually read or write these URLs, but you never know...
Ah in that case, base58 can be useful because it doesn't use characters that may be ambiguous in some fonts (doesn't use: 0/O/I/l , but does use: 1/i)