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
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
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
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 br...@briansmith.org wrote:
Any app that pages
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
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
