David, that's a long-time issue, and I believe there may even be a few bugs
open for it. Twitter has recommended you use the pagination methods for
users with over a certain number of followers (they haven't seemed to be
able to specify what that number is). Unfortunately, as we saw a couple
days ago, even that's not reliable all the time.
On Sun, Sep 6, 2009 at 2:00 AM, David W. <d...@botanicus.net> wrote:
> Hi Jesse,
> Just like to chirp in and say I'm seeing weirdness too. Particularly, /
> followers/ids is taking more than 10 seconds to return for all
> accounts with over 30k followers, or alternatively are failing with
> 401s (using OAuth tokens). Since 10s is the hard limit for AppEngine,
> my app cannot function without making repeated requests (which results
> in hitting another, involves-cash limit, not to mention the unpaid
> development time). My application is subsequently dead in the water
> for the users who rely on it most.
> <abusive rant directed at ops management removed for brevity>
> On Sep 5, 8:40 pm, Jesse Stay <jesses...@gmail.com> wrote:
> > I've disabled all our following scripts until we hear back from Twitter
> > this. Can I pay to get a 24/7 support number I can call for stuff like
> > Jesse
> > On Sat, Sep 5, 2009 at 1:38 PM, PJB <pjbmancun...@gmail.com> wrote:
> > > The fix to last nights 5000 limit to friends/ids, followers/ids now
> > > returns with approximately 1-5% duplicates.
> > > For example:
> > > User1:
> > > followers: 32795
> > > unique followers: 32428
> > > User2:
> > > friends: 32350
> > > unique friends: 32046
> > > User3:
> > > followers: 19243
> > > unique followers: 19045
> > > NEITHER of these figures comes close to matching what is on
> > > Twitter.com. In fact, if I repeat the same calls 10 times for each
> > > user (with no following/unfollowing in between), each result is
> > > usually different.
> > > The duplicates follow either immediately or within 2 or 3 positions
> > > after each other.
> > > What's strange is that the duplicates are NOT the same if the call is
> > > repeated.
> > > Please help.
> > > This bug is new as of this morning.