<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>wahern</author><text>For my current project I decided to try out 120-bit&amp;#x2F;15-byte identifiers. 120 is evenly divisible by 4 (hex), 5 (base32), 6 (base64), and 8. Neither base32 nor base64 encodings need padding. You can usually leave padding out regardless, but with 120 bits it&amp;#x27;s not even a choice you have to worry about, and there are no wasted bits.</text><parent_chain></parent_chain></comment><story><title>Short, friendly base32 slugs from timestamps</title><url>https://brandur.org/fragments/base32-slugs</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kijin</author><text>If you&amp;#x27;re going to change the order defined in RFC 4648, you might as well change the character set, too. Since one of the goals is to minimize the use of characters that can be confused for another, I would add back 8 and 9 and remove two of i, l and o.</text><parent_chain></parent_chain></comment><story><title>Short, friendly base32 slugs from timestamps</title><url>https://brandur.org/fragments/base32-slugs</url></story>