Since Twitter's introduction into the tech community at SxSW, Twitter has gone through a ton of ups and downs. Twitter's downtime has been the talk of the community for several months now. Now, with a lot of heavy hitters on the team, Twitter seems to be on the right track getting its act together.
Lately, Twitter has been more stable than we've ever seen before. Earlier this week Twitter had some scheduled downtime, but apparently it was for a good reason. However Twhirl hasn't been giving me very many errors these days. I also haven't received a "pause" message from Twhirl either. On the other hand, it's recently been announced that Twitter has upped its API limit to 100 requests per hour - with the goal of keeping the limit to least 70. Don't believe me? Check Twhirl.
The biggest question at this point is: will this be consistent behavior from Twitter from now on? While we're sure FriendFeed will be safe from any repercussions, what will this mean for the clones such as Plurk, identi.ca, and kwippy? We'd love to hear your comments about the increase in the API limit and the future of the many Twitter clones.
Comments
Subscribe to comments for this post OR Subscribe to comments for all Read/WriteWeb posts
finally, I was going to cahnge my password
Posted by: Sasha Kovaliov
|
July 10, 2008 2:36 AM
fantastic!
Posted by: Zee from WeDoCreative
|
July 10, 2008 2:40 AM
I'll believe it when it's still working in 2 days time :-)
Posted by: Duncan Riley
|
July 10, 2008 2:43 AM
@Duncan - 2 days time in a row :)
Posted by: Sasha Kovaliov
|
July 10, 2008 2:44 AM
Agreed 2 days...
Posted by: Dave Gray
|
July 10, 2008 2:46 AM
Wow, it was only 70 when I joined in...
Posted by: Yuvi
|
July 10, 2008 2:47 AM
Whoa! I'm awake - just did the pinch test. What does the status blog say the req/hr rate is? (I'm on a mobile and can't check myself.)
Posted by: acedanger
|
July 10, 2008 3:05 AM
The status blog still says the API is limited to 20/hr. But it is early over on the west coast, so maybe there will be an update in a few hours.
Posted by: Rob Diana
|
July 10, 2008 3:16 AM
Was announced on the dev mailing list today: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d9a54ff20fec36d8 (scroll down a bit)
Posted by: Piers | July 10, 2008 3:37 AM
Yeah, I saw @tweetdeck post a tweet about 100 / hr this morning...woo hoo!! very GOOD sign that twitter is making corrections in the right direction....yeah twitter!
Posted by: Susan Beebe
|
July 10, 2008 3:53 AM
I had a bit dificulty in the begining, when I changed the pass word all went well. Works fine now.
Posted by: Tom Lee | July 10, 2008 4:10 AM
I agree this is an improvement. Also I notice that paging through a user's timeline in the API has been re-enabled (on 7th July?) after a long time of being disabled. However there still seem to problems with the caches of API data giving very out of date data (a day or two) and missing fields.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/849f55441abdf59e/9d120e1085c7688f
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/6c1b09be52e4c591/69a5c73b8aa3065e
Also recently there have been problems with 500 errors on posting updates:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4162167e574612a3
So I would say they are on the right track, but not out of the woods yet.
Posted by: Richard Cunningham | July 10, 2008 4:31 AM
Hopefully IM will be back soon!
Posted by: Billy Fairchild
|
July 10, 2008 4:37 AM
Plurk still rocks!
Posted by: LiveCrunch | July 10, 2008 5:04 AM
i'll try my twitter
Posted by: gadis | July 10, 2008 5:17 AM
"Rumors of my death have been greatly exaggerated" - The Twitter Fail Whale
Posted by: Todd | July 10, 2008 7:31 AM
It's nice that they have the API limit moving up, but it still doesn't offer the response time that I desire. When I'm on Twitter, I'm interacting rapidly with people, and I have a lot of stuff flowing by very quickly. I need GTalk integration to work again. Updated right away, without the need for a client to request updates, and I can respond right away. Anything less and my Twitter use is too frustrating.
Twitter @thattalldude
Posted by: Shawn Kirsch
|
July 10, 2008 8:29 AM
100 requests/hour! finally some good news from twitter.
Posted by: Alan Le
|
July 10, 2008 8:36 AM
Does Twitter have an iPhone version of the FailWhale ready for this weekend?
Posted by: Bill Sodeman
|
July 10, 2008 8:43 AM
status blog says 100 req/hr...whoa!
Posted by: acedanger
|
July 10, 2008 11:17 AM
It's been more than a week now and looks like Twitter's still stable. The clones be damned.
Posted by: Rudy | July 17, 2008 4:09 PM