Re:RFC 6920: Naming Things with Hashes
by zAy0LfpBZLC8mAC on Sunday February 21, 2016 @10:13AM
(#11144784)
... in which case my post explains why UUIDs are the better solution.
[ Parent
| on HN ]
Content hashing doesn't rely on timestamps to act as a unique identifier. It relies on all of the content, which may (or may not) include a timestamp, depending on your application. To the degree that collisions occur, that's a feature, not a bug. If you get undesirable collisions, you aren't hashing the right data.
Edit: to clarify, content hashes are just like UUIDs except you can get useful collisions if you want them.