Issue 1019 - twitter-api - Paging broken in followers/ids

Project Home		Issues

Issue 1019:	Paging broken in followers/ids
	8 people starred this issue and may be notified of changes.	Back to list

Status:	Fixed
Owner:	alexfpayne
Closed:	Sep 15
Type-Defect
Priority-High

Reported by WaldronFaulkner, Sep 07, 2009

Now only getting two pages of results when using ?page=x in followers/ids - 
Example: @starbucks (user_id 30973) has nearly 300K followers. 

http://twitter.com/followers/ids.xml?id=30973&page=3

returns no result. Same is true for ?user_id=30973&page=3

Previous issues with paging (eg, not having spam users filtered out) were
annoying, but this is completely broken. High priority, please, this has my
app crippled for users with many followers, and every day that goes by I'm
LOSING data. 

Thank you,

- Waldron

Comment 1 by alexfpayne, Sep 08, 2009

 Issue 1004  has been merged into this issue.

Comment 2 by alexfpayne, Sep 08, 2009

I've reproduced this bug. Agreed, high priority. We'll get on it.

Status: Accepted
Owner: alexfpayne

Comment 3 by WaldronFaulkner, Sep 09, 2009

Thanks, Alex, looking forward to getting my app back online. I notice the priority is
still set to medium, though, any chance we can update this log to reflect high
priority status? I worry that the issue may slip through the cracks if not correctly
labeled. Thanks!

- Waldron

Comment 4 by jugan...@gmail.com, Sep 09, 2009

Have this problem as well. Here's something I noticed.

Z100NewYork has 18,938 followers. For this amount, a followers/ids/
request (without a specified page=) goes through without a failwhale, returning all 18,938.

By comparing:
http://twitter.com/followers/ids/Z100NewYork.xml
http://twitter.com/followers/ids/Z100NewYork.xml?page=1
http://twitter.com/followers/ids/Z100NewYork.xml?page=2

One can see that page=1 returns followers 1-5000, while page=2 actually returns followers 10001-15000. 
(This is what I'm seeing at least). page=3 returns nothing.

This alone is a bug, and seems very related to the more general problem of page=n being broken for n>2.

Comment 5 by WaldronFaulkner, Sep 10, 2009

Hi Alex, any status update on this bug? My business dev. efforts are essentially
off-line, as I can't put a broken product in front of potential customers. Would love
to have an idea of how progress is coming along on this. Also, I notice we're still
"medium" priority. Lots of stars against this bug, it seems to be important to a lot
of API developers.

Let me know if I can be of any help? Thanks!

- Waldron

Comment 6 by c.langreiter, Sep 11, 2009

Please, Twitter folks: This should get high priority indeed.

Comment 7 by alexfpayne, Sep 11, 2009

Agreed.

Labels: -Priority-Medium Priority-High

Comment 8 by WaldronFaulkner, Sep 13, 2009

Hey Alex, can we get a status update? Haven't had ANY info on this since it was
posted. My business development efforts are off line because of it. I need the API
team to understand that my ability to build a business around the Twitter API depends
on this. If I'm going to be left high and dry like this, with no correction (and no
status updates) for weeks at a time, I have to reevaluate whether the platform is
ready for serious development (I mean business dev). PLEASE for the love of god,
address this issue, it's killing me.

Comment 9 by alexfpayne, Sep 15, 2009

Please see the updated documentation for a new pagination mechanism that should be more reliable:

http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-followers%C2%A0ids

Status: Fixed

► Sign in to add a comment