Re: [twitter-dev] Upcoming changes to the way status IDs are sequenced
On 03/26/2010 01:41 PM, Taylor Singletary wrote: > Hi Developers, [snip] > 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'm a mathematician. So yes, I *am* trying to analyze the IDs as other than identifiers. ;-) As long as the status ID generation algorithm is documented - how many bits are timestamp, how many bits are random, what the granularity of the timestamp is, how the Spritzer and Gardenhose sampling is done, etc. - I can do what I want to do without any API additions. -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky "A mathematician is a device for turning coffee into theorems." ~ Paul Erdős 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.
Re: [twitter-dev] Upcoming changes to the way status IDs are sequenced
How will this change affect the "since Status_id" type calls? I am working on a system that will depend on being able to download mentions once and only once, and was planning on using this function to ensure I got only what I wanted. Cheers, Nigel. On 26 March 2010 20:41, Taylor Singletary wrote: > Hi Developers, > > It's no secret that Twitter is growing exponentially. The tweets keep > coming with ever increasing velocity, thanks in large part to your great > applications. > > Twitter has adapted to the increasing number of tweets in ways that have > affected you in the past: We moved from 32 bit unsigned integers to 64-bit > unsigned integers for status IDs some time ago. You all weathered that storm > with ease. The tweetapoclypse was averted, and the tweets kept flowing. > > Now we're reaching the scalability limit of our current tweet ID generation > scheme. Unlike the previous tweet ID migrations, the solution to the current > issue is significantly different. However, in most cases the new approach we > will take will not result in any noticeable differences to you the developer > or your users. > > We are planning to replace our current sequential tweet ID generation > routine with a simple, more scalable solution. IDs will still be 64-bit > unsigned integers. However, this new solution is no longer guaranteed to > generate sequential IDs. Instead IDs will be derived based on time: the > most significant bits being sourced from a timestamp and the least > significant bits will be effectively random. > > Please don't depend on the exact format of the ID. As our infrastructure > needs evolve, we might need to tweak the generation algorithm again. > > If you've been trying to divine meaning from status IDs aside from their > role as a primary key, you won't be able to anymore. Likewise for usage of > IDs in mathematical operations -- for instance, subtracting two status IDs > to determine the number of tweets in between will no longer be possible. > > 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? > > Taylor Singletary > Developer Advocate, Twitter > http://twitter.com/episod > > 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. > 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.
Re: [twitter-dev] Upcoming changes to the way status IDs are sequenced
Yup, I am using since_id as well in my application to perform various sequential tasks. Hopefully new id generation scheme will have this parameter support using some alternatives at least. Alam Sher On Sat, Mar 27, 2010 at 1:48 AM, Brian Smith wrote: > Any app that pages through timelines uses since_id or max_id depends > responses being ordered by tweet ID. What will be the replacement for > since_id and max_id? > > > > Taylor Singletary wrote: > > We are planning to replace our current sequential tweet ID generation > routine with a simple, more scalable solution. IDs will still be 64-bit > unsigned integers. However, this new solution is no longer guaranteed to > generate sequential IDs. Instead IDs will be derived based on time: the > most significant bits being sourced from a timestamp and the least > significant bits will be effectively random. > > > > 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? > > 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. > -- ___ Alam Sher Khan +92 331 505 5549 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.
Re: [twitter-dev] Upcoming changes to the way status IDs are sequenced
> 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 * ckai...@floodgap.com -- 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.
RE: [twitter-dev] Upcoming changes to the way status IDs are sequenced
Any app that pages through timelines uses since_id or max_id depends responses being ordered by tweet ID. What will be the replacement for since_id and max_id? Taylor Singletary wrote: We are planning to replace our current sequential tweet ID generation routine with a simple, more scalable solution. IDs will still be 64-bit unsigned integers. However, this new solution is no longer guaranteed to generate sequential IDs. Instead IDs will be derived based on time: the most significant bits being sourced from a timestamp and the least significant bits will be effectively random. 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? 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.
