We are aware rate limits are being reported incorrectly. We are tracking the issue on the API tracker: http://code.google.com/p/twitter-api/issues/detail?id=1728
Matt On Tue, Jul 6, 2010 at 10:10 AM, Johnson <[email protected]> wrote: > I want to know what's the metrics of this dynamic logout. > I have several twitter account/twitter development accounts. > It started around 1am PST, one of my account keep getting 400. I woke > up this morning, that only account is still getting 400. > I tried a different pair comsumer key/token using twurl, it works. > I tried on mobile, Echolfon, failed, but twitbird goes thru. > Obviously the web works! > What other experiments do u want me to run? > Are twitter giving favor on specific accounts? > > On Jul 6, 9:57 am, Pascal Jürgens > <[email protected]> wrote: > > Just a sidenote: This can be coincidental. Unless you try several dozen > times with each client, no valid inference can be drawn from the tests. > > > > Pascal > > On Jul 6, 2010, at 18:46 , Johnson wrote: > > > > > > > > > I notice that the rate limit is application specific. I've tried a few > > > clients, some of them goes thru, some don't. > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
