3 ms·
> I tend to avoid UUIDv7 and use UUIDv4 because I don't want to leak the creation times of everything. See perhaps "UUIDv47 — UUIDv7-in / UUIDv4-out (SipHash‑m
by throw0101a 10mo ago
> I tend to avoid UUIDv7 and use UUIDv4 because I don't want to leak the creation times of everything.
See perhaps "UUIDv47 — UUIDv7-in / UUIDv4-out (SipHash‑masked timestamp)":
* https://github.com/stateless-me/uuidv47 https://github.com/stateless-me/uuidv47
* Sept 2025: https://news.ycombinator.com/item?id=45275973 https://news.ycombinator.com/item?id=45275973
- wongarsu 10mo agoIf that kind of stuff is on the able you can also use boring 64bit integer keys and encrypt those (e.g. [1]). Which in the end is just a better thought out version of what the article author did. UUIDv47 might have a space if you need keys generated on multiple backend servers without synchronization. But it feels very niche to me. 1: https://wiki.postgresql.org/wiki/XTEA_(crypt_64_bits) https://wiki.postgresql.org/wiki/XTEA_(crypt_64_bits)