Using Twitter4J, and what I've been seeing is last night, getFollowersIDs(), including suspended. This AM, the filtering of suspended accounts seems to be working again.
On the other hand, getFollowersStatuses() doesn't seem to be filtering out the suspended accounts. pg On Sep 5, 7:36 am, Dewald Pretorius <dpr...@gmail.com> wrote: > John, > > Just so we know, is this 5,000 thing going to be fixed over the > weekend, or will we have to wait until Tuesday? > > Dewald > > On Sep 5, 12:35 am, John Kalucki <jkalu...@gmail.com> wrote: > > > We're aware of the problem with the following API not returning more > > than 5,000 followers. Apparently this call has recently been > > unreliable was often timing out and returning 503s. A change to fix > > the 503s limited the results to 5000 followers prematurely. We're > > going to get this back to the >5000 followers, but with 503's state as > > soon as we can, but we're fighting several fires at once tonight. > > > More in a few minutes. > > > -John > > > On Sep 4, 7:56 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > Not only do the social graph calls now suddenly, without any prior > > > warning of announcement, return only 5,000 ids, it is messed up even > > > when you do the paging as per the API documentation. > > > > Case in point. @socialoomph has 16,598 followers. If you page through > > > the follower ids with &page, you get only 12,017 entries. > > > > This is highly frustrating, and it has now completely screwed up my > > > follower processing. It does not help that Twitter has rolled out > > > something into production without any kind of testing, right before a > > > weekend. > > > > Dewald
