Earlier quoted context omitted.
Yes, but the problem with Twitter is they took too much money. You don't need to have $1Billion dollars in financing to offer a service like this -- this is what the likes of app.net are teaching us. A $50million Twitter could have "easily" sustained it's vision/objective without having to cannibalise it's entire ecosystem. However someone promised the moon to a bunch of financiers and now they have to deliver above…
1) How do you know how much money it takes or does not take for Twitter to offer it's service? 2) Don't you think it's a little early to compare app.net and twitter? App.net is in it's infancy and is nowhere near the product twitter is 3) What could Twitter have been exactly? How did closing a few API's off prevent it from getting there? 4) Have you ever imagined that perhaps your vision for Twitter and Twitter's vis…
I don't know how much it takes Twitter (even though it should be relatively easy to find out), but I do have an idea how much it should take.
Twitter presentations suggest 70 million messages per day. 800 tweets per second:
http://www.slideshare.net/raffikrikorian/twitter-by-the-numb...
It's not that much, actually. Some of us have processed 50-70 million transactions per day on a much smaller infrastructure (25..40 AWS boxes) - quite often designed and deployed just days prior to the massive traffic spike, with fancy features like real-time fraud checking etc.
It's not that hard to do what Twitter does. At least, with the amount of financial backing that they have, I don't expect them to be failing in a spactacular fashion periodically.