[twitter-dev] Re: friends/ids now returns w/ 1-5% random duplicates (as of this morning)
Hey Jesse, I've seen random failures and timeouts in the past, but in the last 48 hours they have become very consistent. I've got 4 accounts that have just 'stuck'. Very tempted to just close up the app. David On Sep 6, 9:13 am, Jesse Stay wrote: > 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. 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. > > > > > > David > > > On Sep 5, 8:40 pm, Jesse Stay wrote: > > > I've disabled all our following scripts until we hear back from Twitter > > on > > > this. Can I pay to get a 24/7 support number I can call for stuff like > > this? > > > Jesse > > > > On Sat, Sep 5, 2009 at 1:38 PM, PJB 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.
[twitter-dev] Re: friends/ids now returns w/ 1-5% random duplicates (as of this morning)
So that is why my cron jobs are suddenly taking forever to complete, since Saturday morning. This 10 second delay is a new bug. In the past one just got a lot of 502 errors when retrieving really large accounts, but even those calls were seldom longer than 1 second. Dewald On Sep 6, 5:00 am, "David W." 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
[twitter-dev] Re: friends/ids now returns w/ 1-5% random duplicates (as of this morning)
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. 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. > > > > > David > > On Sep 5, 8:40 pm, Jesse Stay wrote: > > I've disabled all our following scripts until we hear back from Twitter > on > > this. Can I pay to get a 24/7 support number I can call for stuff like > this? > > Jesse > > > > On Sat, Sep 5, 2009 at 1:38 PM, PJB 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. >
[twitter-dev] Re: friends/ids now returns w/ 1-5% random duplicates (as of this morning)
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. David On Sep 5, 8:40 pm, Jesse Stay wrote: > I've disabled all our following scripts until we hear back from Twitter on > this. Can I pay to get a 24/7 support number I can call for stuff like this? > Jesse > > On Sat, Sep 5, 2009 at 1:38 PM, PJB 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.
[twitter-dev] Re: friends/ids now returns w/ 1-5% random duplicates (as of this morning)
I've disabled all our following scripts until we hear back from Twitter on this. Can I pay to get a 24/7 support number I can call for stuff like this? Jesse On Sat, Sep 5, 2009 at 1:38 PM, PJB 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. >
