We're relying on the ID being sequention for a number of purposes: 1) Counting elapsed tweets to estimate tweet rates to feed back into count parameter to backtrack when restarting streaming API/Shadow - how will we be able to do that without sequential IDs???
2) Indexing and sorting pages of tweets to be display by our application - moving away from sequential IDs to break our sorting algarithms... and require recoding to sort exclusively by date alone 3) Polling for new mentions to merge within streamed tweets - we use the ID as a last placeholder - again chnages there would break our app unless recoded. Zaudio Developer BullsOnWallStreet.com To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
