News for hackers. Stuff that matters.
Re:Google Trying to Solve a UUID by jwilk on Saturday August 06, 2022 @10:26AM (#32368380)
Why 23?
Re:Google Trying to Solve a UUID by ericbarrett on Saturday August 06, 2022 @10:48AM (#32368585)
Guessing no I, L, or O to avoid confusion with numbers.
Re:Google Trying to Solve a UUID by Dylan16807 on Saturday August 06, 2022 @01:30PM (#32369946)
At that point I feel like you should just use base32 instead of 33.

For just removing digits-E-digits, that's 10000 patterns for each E position, of which there are 3. Since 36^5 is over 60 million, you're only removing a twentieth of a percent of values. Closer to a tenth of a percent if you remove those values from 33^5 or 32^5.

Re:Google Trying to Solve a UUID by charcircuit on Saturday August 06, 2022 @04:31PM (#32371348)
It's more useful to look at the total amount of values rather than how much the space gets reduced. If you have 10s of millions of values you can have several devices for even the largest employers that exist today.
Re:Google Trying to Solve a UUID by charcircuit on Saturday August 06, 2022 @04:26PM (#32371295)
It was I, O, and E.