Re:Twitter's UID associated to each tweet will very soon exc...
by hugothefrog on Tuesday June 09, 2009 @08:47AM
(#648953)
For a first guess, if there were 5 writing dbs, each could write every 5th id, starting at a different index (0,1,2,3,4).
You'd end up with globally unique ids, and as long as your writes were (approx.) evenly distributed, all 5 sequences would be (approx.) close to each other.
Who knows, they might have 100 writable dbs, with only 70% up at any point in time, meaning only 70% of all integers are actually used.. anyway, I don't know, I can just imagine them doing something like this if they wanted certain things from the system.
Re:Twitter's UID associated to each tweet will very soon exc...
by hboon on Tuesday June 09, 2009 @04:33PM
(#649927)
No. Because their API exposes an explicit ordering of the IDs - there is a sinceID: parameter.
Re:Twitter's UID associated to each tweet will very soon exc...
by Timothee on Tuesday June 09, 2009 @10:48AM
(#649163)
You can get the public timeline from here: http://twitter.com/public_timeline
Note that one can delete a message, which could explain some gaps.
Re:Twitter's UID associated to each tweet will very soon exc...
by jackowayed on Tuesday June 09, 2009 @12:29PM
(#649328)
I think the gaps are mostly people posting protected tweets, which thus don't get into the public timeline.
2088840357 2088840362 (difference of 5, and that's without a real public timeline where you could easily prove each tweet takes the next number in a sequence)
So it isn't as if they're using UUIDs or something unique... they very much seem to be relying on a single counter (currently).