← Back to context Comment by stanmancan 1 day ago I left a more detailed comment on the parent, but it's definitely not impossible! 6 comments stanmancan Reply ryanmonroe 1 day ago The scenario in this post is that the first uuid was created one year before the duplicate uuid. That isn’t possible with v7 ffsm8 1 day ago You're heavily leaning on "collision like this" to relate to the exact time stamps for your statement to be true.It's equality possible to interpret the "like this" to the collision itself, without a focus on the 1 year distance between the creation dates.So I guess both views are valid. calfuris 17 hours ago The inclusion of a timestamp in v7 makes collisions impossible unless the generating systems think that the time is the same down to the millisecond, which makes the temporal distance quite relevant. 1 reply → stanmancan 20 hours ago The scenario being the collision itself, the time period isn’t particularly relevant aside from it occurring much quicker than expected. JamesSwift 1 day ago Surely the scenario where he generates the same number of items as he did between 2025 and now, but did it in 1 tick of v7 UUIDs also runs into it?
ryanmonroe 1 day ago The scenario in this post is that the first uuid was created one year before the duplicate uuid. That isn’t possible with v7 ffsm8 1 day ago You're heavily leaning on "collision like this" to relate to the exact time stamps for your statement to be true.It's equality possible to interpret the "like this" to the collision itself, without a focus on the 1 year distance between the creation dates.So I guess both views are valid. calfuris 17 hours ago The inclusion of a timestamp in v7 makes collisions impossible unless the generating systems think that the time is the same down to the millisecond, which makes the temporal distance quite relevant. 1 reply → stanmancan 20 hours ago The scenario being the collision itself, the time period isn’t particularly relevant aside from it occurring much quicker than expected. JamesSwift 1 day ago Surely the scenario where he generates the same number of items as he did between 2025 and now, but did it in 1 tick of v7 UUIDs also runs into it?
ffsm8 1 day ago You're heavily leaning on "collision like this" to relate to the exact time stamps for your statement to be true.It's equality possible to interpret the "like this" to the collision itself, without a focus on the 1 year distance between the creation dates.So I guess both views are valid. calfuris 17 hours ago The inclusion of a timestamp in v7 makes collisions impossible unless the generating systems think that the time is the same down to the millisecond, which makes the temporal distance quite relevant. 1 reply →
calfuris 17 hours ago The inclusion of a timestamp in v7 makes collisions impossible unless the generating systems think that the time is the same down to the millisecond, which makes the temporal distance quite relevant. 1 reply →
stanmancan 20 hours ago The scenario being the collision itself, the time period isn’t particularly relevant aside from it occurring much quicker than expected.
JamesSwift 1 day ago Surely the scenario where he generates the same number of items as he did between 2025 and now, but did it in 1 tick of v7 UUIDs also runs into it?
The scenario in this post is that the first uuid was created one year before the duplicate uuid. That isn’t possible with v7
You're heavily leaning on "collision like this" to relate to the exact time stamps for your statement to be true.
It's equality possible to interpret the "like this" to the collision itself, without a focus on the 1 year distance between the creation dates.
So I guess both views are valid.
The inclusion of a timestamp in v7 makes collisions impossible unless the generating systems think that the time is the same down to the millisecond, which makes the temporal distance quite relevant.
1 reply →
The scenario being the collision itself, the time period isn’t particularly relevant aside from it occurring much quicker than expected.
Surely the scenario where he generates the same number of items as he did between 2025 and now, but did it in 1 tick of v7 UUIDs also runs into it?