Don't need any app. Everyone can log into the same account at the same
time. Is that the issue?
http://twitter.com/statuses/update.format?source=appname
Here's the typical errors. Call 1 says 132 hits remaining; call 2
returns over the limit. Once an hour, call 2 slips through and returns
the right result. Otherwise, on some accounts - the rate_limit bug
blocks access. On other accounts, there is no problem at all.
Sometimes, the problem resolves
We reported/documented inconsistent, incorrect responses on statuses/
followers, statuses/friends. After a few reboots, to correct
connections that have been left open, all the accounts are working.
We'll be monitoring for any additional problems. Thanks for the fast
response - after our report
Oops. spoke too soon. Still eradic problems - same symptoms. Incorrect
rate_limit response on statuses/followers when ..ids calls work
perfectly on the same account.
After the Saturday reset, here's what we're seeing:
Reliable performance:
- search
- statuses/update
- statuses/user_timeline
- account/rate_limit_status
- ..ids
- friendships/create
Unreliable with frequent fails:
- statuses/followers
- statuses/friends
Returns rate limit error, despite other
Our IP: 69.107.71.66 Your IP: 168.143.162.68 Via ATT Dynamic DSL
We host Twitter accounts for enterprise clients - each via basic
authentication 24x7 via FF3.5. No memory leak observed on FF3.5 -
despite the problems. We're staring at dozens of identical Vista
machines - some work happily,
Every change detail is helpful.
On Aug 13, 12:21 pm, Alex Payne a...@twitter.com wrote:
A day late and a bug short...
- FIXED: /account/verify_credentials no longer enforces a rate limit
that's inconsistent with the rest of the API.
Thanks.
--
Alex Payne - Platform Lead, Twitter,
During the DDOS attack, the Twitter ids fails the most - returning
nothing.
Statuses, friends, and followers calls can also fail, returning random/
incorrect error messages; but less frequently.
Update calls seem to be ok.
FYI
