I was a too busy with work yesterday to realize that Twitter was down for much of the day. Actually, come to think of it, maybe I got extra work done because Twitter was down. Hmmm.
Anyway, I do miss Twitter when it’s down. Along with blogging it’s one way that I keep in track with others online–people I don’t know all that well, but I find fascinating to follow. It’s also one of the channels I use for public micro-conversations with others, such as Warner Crocker, Rob Bushway, and even my sister, Lora. Simply put, Twitter has become a natural part of my online consumption.
So when it goes down, you can often hear me grumble. I miss it. Others do too.
Word is that the Twitter team has tried hard to improve their infrastructure in order to handle their traffic better and, I’m sure, be more robust. I can imagine building out a service such as Twitter is a significant task.
But I’m with Dave Winer here, after repeated outages, us users begin to wonder. What’s going on? Is there something we can help with? Is there something we can do?
Dave suggests that the next step is to open up some communication–maybe a “what’s going on page” and inviting a small group of community tech folks in for some dialog. In the era of blogging, this seems like a good idea. However, particularly for a small company this might be a really good suggestion. Why? It’s a rather simple principle. Because sometimes when you have to explain something, it helps you streamline the thought process and ideas. Further, with all the tech talent out there, someone might have some good suggestions–suggestions not particularly on more things to do (there are always those), but suggestions on things not do to. Things that would help them trim the daunting problem down and keep it even more manageable–something more scaled to the current size of Twitter.
I hope something not too intrusive can be worked out here.
Comments on this entry are closed.