41–50 of 236 posts
Earlier quoted context omitted.
No identifier can guarantee that. We just get close enough to be acceptable. Per Wikipedia, the probability to find a duplicate within 103 trillion version-4 UUIDs is one in a billion. so-youre-saying-theres-a-chance.gif
A billion is not that big of a number for UUIDs
A billion isn't that big a number, but 103 trillion is.
Earlier quoted context omitted.
You can prevent any obscenity, O and 0 confusion, and I and L confusion, just by excluding vowels. If someone interprets "f4g" in an offensive way, then they have bigger issues than can be dealt with in software.
Why we care about obscenity in pseudo-random ids and url?
UUIDv7 has been taking HN by storm for years now! When is it going to become a proper standard, and when are libraries and databases and all the rest going to natively support it?
Earlier quoted context omitted.
> combining time + random number You can't guarantee that this will be globally unique.
No identifier can guarantee that. We just get close enough to be acceptable. Per Wikipedia, the probability to find a duplicate within 103 trillion version-4 UUIDs is one in a billion. so-youre-saying-theres-a-chance.gif
That aside, UUIDv4 is banned in many orgs because there have been several instances in the wild where the “random” number wasn’t nearly as random as advertised from some sources for a variety of reasons, leading to collisions. It is relatively easy to screw this up so many orgs don’t risk it.
https://joist-orm.io/docs/advanced/tagged-ids
We'd used `:` as our delimiter, but kinda regretting not using `_` because of the "double-click to copy/paste" aspect...
In theory it'd be really easy to get Joist to take "uuid columns in the db" and turn them into "typeids in the domain model", but probably not something that could be configured/done via userland atm...that'd be a good idea though.
Earlier quoted context omitted.
A billion is not that big of a number for UUIDs
Re-read. You'd have to generate 103 trillion to have a one billion th chance of a collision. A billion isn't that big a number, but 103 trillion is.
Unrelated, but this links to "Crockford's alphabet", https://www.crockford.com/base32.html , which is a base-32 system that includes all alphanumeric characters except I and L (which are confusable with 1), O (which is confusable with 0), and U (????). The page says the reason for excluding U is "accidental obscenity'. What the heck is it talking about?
what does k-sortable mean?
Earlier quoted context omitted.
Re-read. You'd have to generate 103 trillion to have a one billion th chance of a collision. A billion isn't that big a number, but 103 trillion is.
I think you made a mistake in your math. The Birthday Collision probability of just a trillion random UUID is much higher than that.