|
|
|
|
|
by PabloSichert
2304 days ago
|
|
Hm, that's an interesting choice. I also wonder why they didn't use an encoding that has an alphabet with 2^n characters (that way you can directly map 1 charater to n bits when decoding). Coincidentally, I've just finished some work on a project[1] that is in the same space (identifiers for images). For the reasons you pointed out, I found Douglas Crockford's base32[2] encoding to be a good fit. [1] https://github.com/pablosichert/ciid [2] https://www.crockford.com/base32.html |
|
(83 is about as many safe characters as you can reasonably find, and it allows some nice ways of packing values together.)