Loading Profile...
EMPLOYEE
MacWorld & Twitter slowness + downtime
Hi Guys,
Due to MacWorld and the Steve Jobs keynote, Twitter experienced a flurry of exciting updates and a bit of buckling under the weight of them.
We're currently running a bit slowly as a result, but we're back on track. More information is in the Twitter blog:
http://blog.twitter.com/
We've also made some temporary changes to API handling for the sake of stability, and as a result you may notice some slowness/slow refresh time when using applications such as Twitterrific, etc.
Developers, for more information, you can read @al3x's update in the Twitter Dev group:
http://groups.google.com/group/twitte...
Thanks for your patience, and have fun adding Twitter to your iPhone home screen!
Due to MacWorld and the Steve Jobs keynote, Twitter experienced a flurry of exciting updates and a bit of buckling under the weight of them.
We're currently running a bit slowly as a result, but we're back on track. More information is in the Twitter blog:
http://blog.twitter.com/
We've also made some temporary changes to API handling for the sake of stability, and as a result you may notice some slowness/slow refresh time when using applications such as Twitterrific, etc.
Developers, for more information, you can read @al3x's update in the Twitter Dev group:
http://groups.google.com/group/twitte...
Thanks for your patience, and have fun adding Twitter to your iPhone home screen!
I’m merrily rolling along
5 people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solution from the company
-
Good news for API applications (and their users) everywhere:
We're currently deploying changes to restore the API to its former glory. Expect normal behavior shortly, and if you're a developer, check the Twitter dev list for more technical particulars.
Woo hoo!
I’m optimistic
The company and 3 other people say
this solves the problem
-
Inappropriate?Hi,
I suspect that API changes affected statuses/friends/ requests. I am not receiving responses anymore in my application Twitter Carousel (see main page of http://www.tweets.ning.com). It was working yesterday, but not today. Debugging showing that no response to requests like "http://twitter.com/statuses/friends/" + username + ".json?callback=onLoadFriends", where usrname is Twitter username and
onLoadFriends is function to get response, but it not getting any.
Could you please advice if still possible to get persons who follows specified person.
Thanks.
Jevs -
Inappropriate?Can you restore the API to what it was before the changes so that the Twitter apps that many people use will work again?
I’m frustrated
-
Inappropriate?These are links that go directly to the relevant threads in the Twitter Development Group:
- MacWorld Pain
- Rate Limit still Lowered
Also, if you're a developer, you may want to follow the api_updates Twitter account. They had posted a notice re: the rate limit change on that account earlier. -
Inappropriate?i got only 1 request this hour; snitter updated once, tweetr hasn't shown any updates at all
I’m frustrated
-
Inappropriate?Good news for API applications (and their users) everywhere:
We're currently deploying changes to restore the API to its former glory. Expect normal behavior shortly, and if you're a developer, check the Twitter dev list for more technical particulars.
Woo hoo!
I’m optimistic
The company and 3 other people say
this solves the problem
-
Inappropriate?thanks.... that's good news; yesterday evening things appeared to be working better, however, this morning,I'm back down to only two requests before getting the rate limit notice.
-
Inappropriate?I use flock and twitterific on Mac OS X 10.4 . . . Twitterific is giving me "Twitter returned a 'bad request' error. This happens when you exceed 70 requests per hour. Avoid running other Twitter applications or refreshing too frequently." This is as of today.
I’m frustrated
-
Inappropriate?today, it appeared to work during the 0800 pacific hour; but at 1000, i started getting the same error... It seems to be working during the late afternoon, but not during the morning...
-
-
3 Comments Add a comment
This solves the problem
-
"70 requests" sounds like you've hit Twitter's API limit of 70 authenticated requests per user per hour. That message appears when you're using a third-party Twitter application and have made more than 70 requests in an hour.
There's a separate thread that talks about a potential problem with the API limit in case you'd like to check it out. -
The related thread is found here: http://getsatisfaction.com/twitter/to...
-
The related thread is found here: http://gsfn.us/t/ebb (reposting since my first attempt didn't produce a full URL.)
