ample.
A decision please.
Cheers,
Steve
On Jan 8, 9:24 pm, "st...@implu.com" wrote:
> Here's some rough numbers...x is the number of twitter user's with a
> follower count of...
>
> x >= 100k 714 0.007%
> 75k <= x < 100k 151 0
9 96.529%
Total: 10,369,396
So I would agree that 100k would be sufficient for our needs.
-Steve
On Jan 8, 3:38 pm, Dossy Shiobara wrote:
> 100k, at the minimum.
>
> On 1/8/10 3:35 PM, Wilhelm Bierbaum wrote:
>
> > How much larger do you think makes it easier?
>
> >
I would agree with several views expressed in various posts here.
1) A cursor-less call that returns all IDs makes for simpler code and
fewer API calls. i.e. less processing time.
2) If we must have a 'cursored' call then at least allow for cursor=-1
to return a larger number than 5k.
-Steve
On
This is more like Issue 547: statuses/friends & followers - page
bug
http://code.google.com/p/twitter-api/issues/detail?id=547&q=statuses%2Ffriends&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
-Steve
On Jul 28, 6:53 pm, chinaski007 wrote:
I'm experiencing the same issue with implu. With 14,408 follows, I
should go up to
page 145. However, the last page of data is 101 and 102 onwards
returns nothing.
http://twitter.com/statuses/friends/implu.xml?page=102
The following call does seem to return all the friends/ids however.
http://t