-
The RFC provides documentation for both[ millisecond and microsecond-level precision](https://datatracker.ietf.org/doc/html/draft-peabody-dispatch-new-uuid-format-01#section-4.4.4.1). It would be fun …
-
-
I'm concerned that the usage of `Date` is not monotonic. I've tested this myself and `Date` can give back the same datetime when done very closely.
Furthermore if the OS clock drifts or is set back…
-
> And I don't expect a very long lifespan for 128 bit UUIDs. It is very likely that in 50 or 100 years, 256-bit identifiers (or something radically new) will be used.
160-bit identifiers would be g…
-
[Edit: 'did my math wrong. "90 bit" -> "86 bit" throughout]
Observation: Clock precision is not the same as clock accuracy. Even in systems that provide micro or nano-second precision timestamps,…
-
# Goals:
1. Be collision-free
**It is most important!** If the format is to be widely used, even low collision rates can be dangerous. UUID with a timestamp has much less entropy than UUIDv4. 128 bi…
-
On [uuidv7-python](https://github.com/uuid6/prototypes/tree/uuidv7-python) branch reuses the same `_last_timestamp` between all versions. Maybe it would be better to store two different "last timestam…
-
While having a look at the python prototype and reading the "UUIDv6 Basic Creation Algorithm" section of the draft I noticed a difference between them.
From Section 4.3.4.
> 9. If the state …