Going nuts on 1.1/lists/subscribers.json Cursor issue?

[PaulCroubalian]

According to docs, 1.1/lists/subscribers.json can have a maximum count parameter of 5000, and defaults to 20.

If I use 1000 to limit calls to Twitter servers, the same cursor just loops and crashes the script. It actually looks like the call returns nothing.

Right now, all the script does is echo values to screen. It can’t even do that after the initial pass.

If I cut the count parameter to 10 it works fine. It loops through successive cursors quite nicely. I hate to make that many calls though.

Has the max value changed? Is there a “safe” value?

Please advise

Paul

[PaulCroubalian]

Playing with it… count = 500 works. 600 works, 700 dies

[andypiper]

Will have to check on this. Just to confirm…

• are you able to provide example user / list IDs?
• does this also happen using e.g. twurl?

[PaulCroubalian]

It works the same across all lists I tried it on (20+) I used Mashable’s Social Media Managers list since it’s a good average size. I had the IDs, but I didn’t keep them.

It’s strange. The script worked flawlessly for 7 months, then boom.

I can live with 600 per call. It’s more for Twitter’s sake than mine.

Paul

[andypiper]

That’s odd - I’m not seeing the same thing here, using twurl.

Here’s my test case:

for i in 200 300 400 500 600 700 800 900 1000 2000 5000 6000
do
twurl "/1.1/lists/subscribers.json?include_entities=false&skip_status=true&slug=social-media-managers-24&owner_screen_name=mashable&count=$i" | jq '[.users[]] | length'
done

output:

200
300
399
498
598
696
796
892
989
1569
1569
1569

Note that the numbers start to not match the counts at a certain point, presumably due to protected accounts being on the list.

[PaulCroubalian]

Hummm, maybe I should switch. I’m using tmhOAuth now.

Still, I wonder what happened about 3 days ago that made it stop working

Paul