Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs

Re:Type-safe, K-sortable, globally unique identifier inspire... by inopinatus on Thursday June 29, 2023 @06:22PM (#36527637)

The specification of crockford32 is at https://www.crockford.com/base32.html

z-base32 has some nice ideas, although I don’t really give a damn how these things look except where that has functional/ergonomic consequences, since none of them have real aesthetic value. The beauty of numbers is in their structural properties, not their representations. If we really cared about how it feels I’d suggest using an S/KEY-style word mapping instead to get some poetry out of it.

[ Parent | on HN ]

Re:Type-safe, K-sortable, globally unique identifier inspire... by yencabulator on Thursday June 29, 2023 @06:28PM (#36527710)

Ah, "Hyphens (-) can be inserted into symbol strings." If you don't like 'em, don't use 'em.

And the only point of these encodings is to be more human-palatable than base64. If you take that goal out of the equation, just use base64, it's better (denser, more readily supported everywhere). Various base32's and base58 exist because base64 was not human friendly enough.

[ Parent | on HN ]

Re:Type-safe, K-sortable, globally unique identifier inspire... by inopinatus on Friday June 30, 2023 @07:34AM (#36533111)

Thanks for your advice.

[ Parent | on HN ]