3 ms·
Not good if you’re using them in a situation where they are visible to the public (eg urls) and you don’t want to leak the time component.
by minitoar 6y ago
Not good if you’re using them in a situation where they are visible to the public (eg urls) and you don’t want to leak the time component.
- andy_ppp 6y agoIf you really need this why not add a public ID...
- mnahkies 6y agoTrue, but for many entities the time they were created is basically public information anyway - time of a tweet, date hacker news account was created, time blog post was published. It might leak more granular information than would be publicly available otherwise, but for many use cases it's not a security concern as far as I can tell
- minitoar 6y agoYes, this only matters if you don’t want to leak the time component, eg to thwart people from estimating how many total active users you have.