For a little side project, I build uuid7.com almost entirely with the help of AI tools. Check it out!
I also built the stack with Docker Compose. I have resisted Docker for so long because it was such a paint for homelab type stuff. But I recently started needing to use it at work (we are migrating to AWS Kubernetes – yay! not) so I figured I’d give it a go.
With the assistance of ChatGPT, I put together a full Docker stack using Cloudflare tunnels (cloudflared), Nginx as the webserver, and Flask as the backend all in a couple hours. It works great!
That said, it is running on my main desktop at home to see if it’s a popular site so fingers crossed it holds up.
6 replies on “UUIDv7 site launched!”
Update the link: https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122bis/
done
Hi, I enjoyed the uuid7.com site pretty much, and congrats to the tech stack!
However; if I plug the UUID7 example from the RFC document — 017F22E2-79B0-7CC3-98C4-DC0C0C07398F — into your site then it returns as date:
> UUIDv7 is valid with time: Fri, 24 Sep 1982 20:31:35 GMT
while the example in the RFC document says it should be:
> The timestamp is Tuesday, February 22, 2022 2:22:22.00 PM GMT-05:00
Any idea what could cause this discrepancy?
Thanks! I will look into the discrepancy!
I am using uuid7 – https://github.com/stevesimmons/uuid7. It appears this version uses 60 bits of time, which gives resolution down to 50 nano seconds, instead of the millisecond resolution given in the example. The spec seems to pretty clearly indicate that it should have milliseconds since Unix epoch. Not sure why this implementation uses more time resolution and less randomness.
Ah, ok, there is already an issue/PR open to fix it:
https://github.com/stevesimmons/uuid7/issues/1
https://github.com/stevesimmons/uuid7/pull/2
So this should hopefully be resolved soon!
Keep up the good work! ❤️