Twitter: when all else fails, blame your users.

You’ve probably seen it all over your feed reader today; blogs screaming “Twitter just called Scoble out!”, or “Twitter is punishing their most popular users!”, and frankly they’re right. Alex probably thought he was doing the right thing and taking a proactive approach by explaining things in his blog post yesterday, but he made some poor choices that Twitter is going to have to face this weekend- namely, stating that a factor of the huge downtime issues Twitter has been having is users like Scoble who have tens of thousands of followers are causing database calls in the system to pile up.

As Scoble so eloquently put it in a Seesmic video response to the blog post today, bullshit.

Now, to be clear; Alex didn’t call Scoble out explicitly. It was inferred by the fact that, well, Scoble is pretty much king of Twitter in terms of followers. It was him and a handful of other users (who, it should be pointed out, would also qualify as these evil-doers to the system) made Twitter by singing it’s praises.

More to the point, the blog post is bullshit because it doesn’t explain why Twitter has been having constant issues since day one, long before Scoble and others amassed their base of thousands of followers. Even more so, it doesn’t explain how Twitter is going to fix these issues. So the database is backing up… how are you going to resolve this? Throw more servers at it? Get rid of your ridiculous XMPP-based message backend? Rewrite the site in a language that is actually scalable? For a post entitled questions and answers, there were far too few answers and way too much finger pointing. Let’s be clear what Twitter is: it’s a shit ton of text flying around, and a bunch of databases to store it in. This isn’t that complicated.

Alex isn’t a bad guy, or an idiot. I don’t think his intention was to make it seem as though Twitter is calling these people out. However, Alex isn’t a PR guy. He’s a developer. And, speaking from my own perspective as a developer, we shouldn’t be put in charge of trying to explain things to customers, users or the press. We aren’t good at sugar coating things, or explaining problems to users in a way that makes it consumable. We’re quick to blame the users because, well frankly, it’s usually user error that’s the problem. But users don’t want to hear that- they just want to know when it’ll be fixed.

That said, that blog post should never have been let out the door. Filters should have been put in place to ensure that comments like those in the post never made it live, or at least not when there’s so much anger over Twitter’s complete and total failure to it’s users these past weeks… months… in some people’s eyes, years.

The road to hell is paved with good intentions, and Alex just added another cobblestone to the trail.

But, people, let’s not get crazy here. Realize the intention of the post and try and take it for what it was. Realize that Twitter is better than it used to be in most regards. Realize that Twitter is a free service, and if you’re as sick of it’s downtime as I am, there are plenty of reasonable alternatives. Let’s not all get our panties in a bunch because we don’t know what our friends are buying at the grocery store, or what movie they’re renting tonight, or what project at work is pissing them off. Unless you’re Scoble, or Rose, or Laporte, or Calacanis or even Obama and have thousands upon thousands of users, you weren’t called out, and you shouldn’t take offenses. If you are one of those individuals, you have every right to be, and I would be too. You brought the users to Twitter, you can take them away. And I suggest you do.