Hi, John Does Twitter still plan to implement backfill support in streaming API? In an older post from Mark McBride (April, 2010), he said:
"To alleviate some of the concerns raised in this thread we thought it would be useful to give more details about how we plan to generate IDs ... ... 4) We will provide a way to backfill from the streaming API. ..." Thanks! On 28 set, 18:34, John Kalucki <j...@twitter.com> wrote: > Tomorrow, Wednesday September 29, at 10:00 AM PDT / 17:00 UTC, we will > briefly introduce a field called new_id to statuses delivered over > theStreamingAPI. If this 10 minute test is successful, we will enable > the new_id field continuously on Thursday September 30th at about the > same time. Note that timelines returned by the REST and Search APIs > will not contain this field. This new_id field will allow applications > to preview thenewstatusidgeneration scheme before the primary key > transition scheduled for Tuesday October 12th. > > For more information on our statusidtransition: > > http://groups.google.com/group/twitter-api-announce/browse_thread/thr...http://groups.google.com/group/twitter-api-announce/browse_thread/thr... > > -John Kaluckihttp://twitter.com/jkalucki > Twitter, Inc. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
