Although million follower accounts are rare, how to I design for a
million follower user logged into my application which users Social
Graph API?
If Barack Obama were to log into my application, it would take 566 API
calls to fetch his 2,828,782 followers, but I wouldn't have any left
after t
Check out the section about whitelisting:
http://apiwiki.twitter.com/Rate-limiting
Abraham
On Wed, Dec 9, 2009 at 02:44, Alan Gutierrez wrote:
> Although million follower accounts are rare, how to I design for a million
> follower user logged into my application which users Social Graph API?
>
A cursor should be valid forever, but as it ages and rows are removed, you
might see some minor data loss and probably more duplicates.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Wed, Dec 9, 2009 at 12:44 AM, Alan Gutierrez wrote:
> Although million follower accounts
* John Kalucki [091209 09:28]:
> A cursor should be valid forever, but as it ages and rows are removed, you
> might see some minor data loss and probably more duplicates.
Out of curiosity, what is a cursor? From our (the users') perspective,
it's just an opaque number. But I'm curious. How is
A cursor is an opaque deletion-tolerant index into a Btree keyed by source
userid and modification time. It brings you to a point in time in the
reverse chron sorted list. So, since you can't change the past, other than
erasing it, it's effectively stable. (Modifications bubble to the top.) But
you
