For stack decisions, I needed a non-sequential ID format to prevent users from guessing other IDs. My options were:

• UUIDs v4 that look like this: 496a52cd-49ba-4424-99d9-344e44803cb1
• Hashids that look like this: xpAYDx0m
• Flake IDs whose Mastodon Ruby implementation looks like this: 101151084044583231

I eventually chose flake IDs, because IMO they are better-looking and easier to type.

Although they are meant for distributed systems at scale (think Twitter), for my feature I only cared about how nice they looked. As a bonus, because the first few bits are time-based, they "feel" like good old incremental IDs. #StackDecisionsLaunch