> For the majority of applications we think this scheme switch will be a > non-event. Before implementing these changes, we'd like to know if your > applications currently depend on the sequential nature of IDs. Do you depend > on the density of the tweet sequence being constant? Are you trying to > analyze the IDs as anything other than opaque, ordered identifiers? Aside > for guaranteed sequential tweet ID ordering, what APIs can we provide you to > accomplish your goals?
I don't use the IDs as anything other than identifiers, and I can certainly sort an unordered stream, but I really do need since_id to work the same way it does now. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- LET'S GO FORWARD ... INTO THE PAST! ---------------------------------------- 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.
