This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
Bigger number space #98
Comments
Do you mean
where P. S. There was a similar idea to use 0b111 variant with no version filed: #26 |
Thank you, it's indeed a duplicate of the conversation |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thinking about how to increase the space to reduce collisions, see #23 (comment), I have been wondering if it wouldn't be possible to utilize two (a bit more out-there) concepts to increase the number space available and viability a little.
For one, as far I can see in rfc4144#4.1.3 the MSB 0 is not yet used and in this draft adds the version
0b1000
. What if instead the language was changed to use MSB 0 as indicator for this version and MSB 1 ~ 2 for thevar
add MSB 3 to the random block and do the same for the 2 var bits.This would increase the random space to 77 bits, not quite on the 80 bit level of ULID but it should still be significantly more practicable?!
The text was updated successfully, but these errors were encountered: