Yes, because UUIDv7 gives up some random bits in order to include the timestamp,... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

jubilanti 4 months ago | parent | context | favorite | on: Ask HN: We just had an actual UUID v4 collision...

Yes, because UUIDv7 gives up some random bits in order to include the timestamp, which is done in a way that makes UUIDv7s quick to sort by timestamp.

ai_slop_hater 4 months ago [–]

How does including the timestamp expose me to adversarial exploitation?

danpalmer 4 months ago | | [–]

It reveals the time you created the UUID, for one. That can lead to a bunch of problems.

devmor 4 months ago | | | [–]

The same way using an auto increment integer ID does, but imagine that integer also leaked your created timestamp column too.

goalieca 4 months ago | | [–]

I’ve not come across any.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact