Twitter stumbles, and there goes the neighbourhood

Witness the emotional committment of Twitter users.  Wow, people love it, really want this thing to work, and really love to moan about it as the fail whale displays more and more often.

Twitter looks back on track after a shaky few days back there, which shows that all is not well in microblogging land, and there’s something wrong with the microblogging model, but that’s a topic to take up later.

Having Twitter get slow, turn off features, or just not respond has started to get really annoying.   We’re inclined to include Twitter as an emerging tool to use to build and attract community. But without stability, it’s not going to work predictably . How can we recommend building twitter into a social media campaign?  Well, we can’t really.  Or we have to accept Twitter as a somewhat flaky, sometimes useful tool.

And worse, with Twitter going up and down, there goes the neighbourhood.  People pick up and leave to one of the fifty other microblogging services that are growing up in the shadow of twitter and waiting for users to fall out of the Twitter tree.

Trouble.  We’re never going to find each other if we’re spread across tens of different services.

But then again, we want Twitter, in its lovely cuteness, to work.  But that makes it a monopoly with a secret or currently secret business model.

Tricky.

So, my big needs in microblogging are:

1. I want something reliable that works
2. I want something that accesses most people (that want to be involved)
3. I want it to be long term sustainable, not a monoculture or monopoly with a secret business model

To meet these three, we’re going to need to do some internet-level architecture work to support microblogging and ambient status.  Basically, we’re going to need to:

1. Develop some standards for microblogging messaging
2. Develop standard ways to connect microblogging services together
3. Allow users to migrate from one service to another easily– and use more than one service at once
4. Ensure some level of reliability in messsaging
5. Make sure the whole thing can scale up to the current level of global SMS usage and beyond

This looks a lot like what we have for the internet email architecture.  It took a long time to get organised, and it has some problems, but it is a mostly universal service with lots of servers, providers and clients.

There are a bunch of people talking about these sorts of standardisation. I’ll review the efforts in a later post and see where we are headed.  My guess this is going to take a while and we are going to have some early-adopter pain in the meantime.

Key point:  At some point Twitter is going to have to open up and interwork with other microblogging services.  And that is the moment, in my opinion, when they will really succeed.