If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

Before I start rambling, I’d like to start off by saying that I never really got into the whole microblogging scene. I tried, time and time again, but it just never kept me interested for very long. Maybe that’s why one day I went as far as getting down on my knees and begged God for microblogging to go away so that I wouldn’t have to keep hearing about the latest Twitter outage from all my favourite news sites. As time went by though, I quickly realized that Twitter, and microblogging in general, was here to stay. That’s why today you’re seeing me post my first ever microblogging-related story, and as much as I find the whole ongoing development very interesting, it will probably be my last.
So why do I say that Facebook could kill off Twitter? Well, because it had microblogging before Twitter was a baby (yeah, I know, Twitter still is a damn baby). You can argue day and night that wall-to-wall posts aren’t mini blog posts, but you can’t deny that Status Updates are exactly what Twitter has been doing from the very start. Think about it. Status Updates = Tweets. Don’t believe me? Well, there is one difference between the two, and this is really the key to microblogging’s success. On Twitter, you can follow anyone you would like, without their approval. Facebook just won’t let you do that.

read more @ neowin.net

Twitter has stopped sending SMS updates to UK customers, thus leaving them unaware of the latest important updates on what their friends had for breakfast. Twitter is a service for bloggers who can’t string a sentence together and who want to appeal to readers who can’t focus beyond a headline. Updates can be sent in over SMS message, limited to 140 characters, and are bounced out to interested parties.
The problem, for Twitter, is that sending SMS messages is an expensive business in Europe, even when they are purchased in bulk, and if an incoming message is bounced out to 10 "friends" then Twitter has to pay to send those ten messages. But while in Europe the sender has to pay the full cost of message delivery, as getting messages is free, in the USA received messages are deducted from the tariff bundle, so Twitter can continue to offer the service there. Back in Blighty, however, it’s just too expensive.

View: The full story @ The Reg

Twitter’s struggles with handling high user load have been well documented. To help the embattled site stay up between Fail Whales, they’ve at times reduced features to just try and keep afloat, blocking the replies tab, reducing pagination, and blocking Instant Messaging, for example.
They’ve also visibly tweaked the rate for authenticated API hits, first down from 70 to 20 and back up to 100. But until recently, unauthenticated API requests were unlimited, which all changed Wednesday night around 5 p.m. Pacific Time, when Twitter ratcheted them down to the same 100 per hour per IP address, effectively crushing many external services that relied on Twitter for their data. And this was done without public mention on the Twitter blog.
As you can see in this Google Groups thread, Alex Payne of Twitter told developers last Thursday:

"In our continued effort to keep things fast and prevent abuse we’re planning on introducing rate-limiting by IP for unauthenticated API requests. We’ll allow 100 unauthenticated requests per IP per hour, just as we currently do with authenticated requests. Please let us know if you foresee any ghastly issues with this change."

And while that sounds all nice and dandy, there were a number of developers who did see "ghastly issues", ranging from Kee Hinckley, CEO of Somewhere, Inc., Richard Cunningham of FriendBinder, and Joel Strellner of Twitturly, each of whom runs a product that depends strongly on unauthenticated API requests from the microblogging service.
But it didn’t stop Twitter from making the change, even as Jodee Rich of PeopleBrowsr wrote, "this will blow us out of the water."
Since throttling down the unauthenticated API requests, services that rely on this data are a mere shadow of their former selves.

Twitturly says on status page: "Due to recent changes in Twitter’s API, Twitturly is slowly dying."
Similarly, Twist’s Twitter charts only show a fraction of the data they did at the beginning of the week. (See: "morning", "starbucks" and "computer".)

Twist’s Twitter Search for "Morning"

Twist’s Twitter Search for "Lunch vs. Dinner"

In response to the changes, FriendBinder’s Cunningham said he will now be changing all API requests to Twitter to be authenticated, to work around the problem. He wrote me, in an e-mail, "There are also some parts of the API we cannot even attempt now. User authenticated requests limits are shared with other sites that the user has used - so we might not be able to get any updates for them if some other site hit the limit for them."
You can see this yourself by trying sites that aim to help you bulk follow those Twitter users who are following you. If you use a site like Twitter Karma, and then try to use Less Friends, you will get a nasty note that says you have exceeded your 100 requests per hour limit. And if you’re like me, having fallen way behind on following folks, you might be revisiting one of these sites religiously every hour for the next few days until you’re caught up.

Less Friends and Twitter Karma Get a Mere Fraction of the Updates

Last month, Jesse Stay wrote that developers were bailing on Twitter, thanks to outages and broken APIs. With changes like this, despite improved uptime of late, the end to Twitter’s problems is nowhere in sight, and services that hoped to tap into their API this way are sore out of luck.