My favorites | Sign in
Project Logo
       
New issue | Search
for
| Advanced search | Search tips
Issue 613: followers/ids "?page=" feature returning random number of followers!
17 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  m...@twitter.com
Closed:  May 27
Type-Defect
Priority-High
Component-REST


Sign in to add a comment
 
Reported by amerk86, May 23, 2009
I am trying to get the list of followers for a script I'm working on. When
I get the full list in JSON/XML format, all is great. When I try to use
pagination (?page=x) it acts weird.

I tried to obtain the list of TechCrunch and this is how it works for the
first few pages:
Request URL (http://twitter.com/followers/ids/techcrunch.json?page=1),
returns 5000 results
Request URL (http://twitter.com/followers/ids/techcrunch.json?page=2),
returns 15000 results!!
Request URL (http://twitter.com/followers/ids/techcrunch.json?page=3),
returns 20000 results!
(the next few seem to be consistent, somewhat! Increasing 5k per request)
Request URL (http://twitter.com/followers/ids/techcrunch.json?page=7),
returns 38464 results!!
Request URL (http://twitter.com/followers/ids/techcrunch.json?page=10),
returns 53814 results!!

It's obviously a defect!

Isn't it supposed to return 5000, 10000, 15000 and so on, or - even more
reasonably - 5000 per page without including the previous one? 

Thanks...

Comment 1 by jmathai, May 25, 2009
Same problem here:
jmathai@[~]: curl http://twitter.com/friends/ids/barackobama.xml?page=1 | wc -l
5003
jmathai@[~]: curl http://twitter.com/friends/ids/barackobama.xml?page=2 | wc -l
15003
jmathai@[~]: curl http://twitter.com/friends/ids/barackobama.xml?page=3 | wc -l
20003
Comment 2 by m...@twitter.com, May 26, 2009
Definitely looks like a bug. I'll look into it.
Status: Accepted
Owner: m...@twitter.com
Labels: -Priority-Medium Priority-High Component-REST
Comment 3 by m...@twitter.com, May 26, 2009
Definitely looks like a bug. I'll look into it.
Comment 4 by m...@twitter.com, May 26, 2009
 Issue 621  has been merged into this issue.
Comment 5 by m...@twitter.com, May 26, 2009
I believe I have found the root cause and have a fix. Testing that and putting it up for a review.
Comment 6 by m...@twitter.com, May 26, 2009
 Issue 518  has been merged into this issue.
Comment 7 by m...@twitter.com, May 26, 2009
 Issue 362  has been merged into this issue.
Comment 8 by m...@twitter.com, May 26, 2009
Code reviewed and awaiting deploy.
Comment 9 by m...@twitter.com, May 27, 2009
Fix deployed.
Status: Fixed
Comment 10 by amerk86, May 27, 2009
I think it's working fine now. Thank you for the speedy fix :)
Sign in to add a comment

Hosted by Google Code