Re:Twitter IDs to roll past 53 bits in a couple days (may br...
by jonhohle on Tuesday November 23, 2010 @04:10PM
(#1935374)
I prefer my ID's universally unique. I worry that globally unique ID's won't scale as we begin to colonize other planets. (yes, its a joke.)
Re:Twitter IDs to roll past 53 bits in a couple days (may br...
by tjpick on Tuesday November 23, 2010 @10:41PM
(#1936413)
Stating it is a joke kind of ruined the joke.
Re:Twitter IDs to roll past 53 bits in a couple days (may br...
by ryansking on Tuesday November 23, 2010 @07:44PM
(#1936017)
we don't use incrementing ids, but needed ids that increase over time (so that you can sort tweets by them). hence, snowflake: http://github.com/twitter/snowflake
Re:Twitter IDs to roll past 53 bits in a couple days (may br...
by mayanklahiri on Tuesday November 23, 2010 @07:53PM
(#1936040)
You don't even need to go that far. For non-critical applications (i.e., your web app), you can randomly generate a small string, say 12 bytes, using base-62 characters (A-Za-z0-9) to serve as a probably unique user ID (with VERY high probability).
Re:Twitter IDs to roll past 53 bits in a couple days (may br...
by wahnfrieden on Wednesday November 24, 2010 @06:13AM
(#1937054)
Heard of GUIDs? Make part of it a timestamp, and the chance of collisions goes down astronomically further.
Re:Twitter IDs to roll past 53 bits in a couple days (may br...
by mayanklahiri on Friday November 26, 2010 @12:49PM
(#1942827)
In some cases, including a timestamp in an ID can be giving away information considered private. Sure, you could just hash the resultant ID, but then you're getting back to random digits anyway.
http://www.ietf.org/rfc/rfc4122.txt
uuids are made just for this purpose, string based, never bigger than 40 characters (with dashes and curly braces).
Most products use uuids or Microsoft's name for them guids.