I assume from this then it is still a sortable incremental number
(albeit not sequential) and we can insert id's in an order. For
example if you want to create a combined timeline of two users you
grab both timelines, compare status id's and insert in the order of
them
On Jun 2, 5:22 am, Hwee-Boon Yar hweeb...@gmail.com wrote:
So, does this mean (to paraphrase):
IDs will remain sorted *all* the time except when comparing between 2
tweets sent within 1 second apart, the order *might* be reversed. And
therefore, for most Twitter apps, no change is necessary?
--
Hwee-Boon
On Jun 2, 10:00 am, themattharris thematthar...@twitter.com wrote:
Hey everyone,
In March we sent a message to you about upcoming changes to the way
status IDs are sequenced (http://bit.ly/upcoming-status-id-changes).
Today we announced Snowflake - the service we will be using to
generate those new IDs.
It isn't going live yet! We just know a lot of you are concerned about
how the Tweet IDs are going to affect your applications and wanted you
to have the chance to familiarize yourself with how Snowflake works.
You can find the a link to the code and read more about Snowflake on
the Twitter Engineering blog:http://bit.ly/announcing-snowflake
Best,
Matt
