Peter Bourgon

> Can you elaborate @peterbourgon? My understanding is that the ULIDs are not UUIDs and UUIDs are not ULIDs for the simple reason that UUIDs have version/variant, and ULIDs do...

The monotonic algorithm suggested by the spec is somewhat näive, and has resulted in a lot of confusion and discussion among consumers and implementors. [An example here](https://medium.com/zendesk-engineering/how-probable-are-collisions-with-ulids-monotonic-option-d604d3ed2de). In fact the...

@alizain In the last few months, I've seen multiple instances where developers cited this (flawed) approach for monotonicity as an authoritative source of truth, and made similar mistakes in their...

@ssg You're right. ULIDs are sortable/monotonic _only to some precision_. By default that precision is 1ms as defined by the relevant system clock, but of course there's no guarantee of...

I have an idea, but I'm not yet sure it's feasible. @bboreham @ChrisHines — could you provide a small program that demonstrates the problem cases you've got in mind?

@bboreham Thank you!

@bboreham Do I understand correctly that you don't want the [current output](https://go.dev/play/p/XfgKRPEALCW) of ``` ts=2009-11-10T23:00:00Z caller=prog.go:19 msg=hello ts=2009-11-10T23:00:00Z caller=prog.go:11 msg="important hello" ``` and instead want ``` ts=2009-11-10T23:00:00Z caller=prog.go:19 msg=hello ts=2009-11-10T23:00:00Z...

I'm sharing this experiment rather prematurely in order to solicit feedback. [Here's the gist](https://gist.github.com/peterbourgon/1175b5605bf4b8eb0aef5c12e26988b4). And here's the gist: The basic idea is to embed more "smarts" into the logged value....

Interesting. I think the relevant rules are > When decoding, upper and lower case letters are accepted, and **i and l will be treated as 1 and o will be...

@tsenart Think we can add those things?