Streaming API test: Adding new_id field to statuses at 17:00 UTC Sept 29

3 views
Skip to first unread message

John Kalucki

unread,
Sep 28, 2010, 5:34:00 PM9/28/10
to twitter-deve...@googlegroups.com
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 the
Streaming API. 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 the new status id generation scheme before the primary key
transition scheduled for Tuesday October 12th.

For more information on our status id transition:

http://groups.google.com/group/twitter-api-announce/browse_thread/thread/daf6298d0fdcbc87
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/7982e3b037eeef95

-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.

Walter Santos

unread,
Oct 4, 2010, 12:28:55 AM10/4/10
to Twitter Development Talk
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.

John Kalucki

unread,
Oct 4, 2010, 3:12:20 PM10/4/10
to twitter-deve...@googlegroups.com
I dug back to Mark's email for context, but I still can't puzzle out
what Mark was referring to and what you are asking for. The answer
might be buried somewhere in that 74 message thread. Could you restate
your question?

Does the count parameter do what you need?

-John Kalucki
http://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
>

Reply all
Reply to author
Forward
0 new messages