4 ms·
See also the Bubble Babble encoding (2000) [1] that is essentially the same idea. Note that they are only useful as private identifiers because as public identi
by lifthrasiir 8y ago
See also the Bubble Babble encoding (2000) [1] that is essentially the same idea. Note that they are only useful as private identifiers because as public identifiers you can't avoid them spelling profanity; many geocoding systems entirely forwent vowels for that reason [2].
[1] http://wiki.yak.net/589 http://wiki.yak.net/589
[2] https://github.com/google/open-location-code/wiki/Evaluation-of-Location-Encoding-Systems https://github.com/google/open-location-code/wiki/Evaluation...
- femto113 8y agoI (re)discovered a similar scheme about 7 years ago for encoding numbers based on the observation that 20 consonants + 5 vowels offers essentially the same information density as base 10 numbers. Excluded 'c' because it seemed the most redundant (with 'k' and 's'). I've found it particularly useful for generating random temporary passwords that can be communicated verbally rather than needing to be emailed. https://github.com/femto113/node-pronounceable https://github.com/femto113/node-pronounceable