> Twitter went through severe growing pains to reach the point where it could handle that much traffic; there's no reason to believe App.net won't have to go through similar issues if/as it grows.
Actually, there is: app.net could just observe what twitter did.
And twitter didn't have to go through it either; There's discussions going on about that since 2008 when their uptime suffered outage after outage; here's something I wrote 2 years ago, for example: http://www.reddit.com/r/programming/comments/b2u6t/twitter_o... and I had given that same answer before several time in other forums.
> Any centralized system that has to support tens or hundreds of millions of users in real time is going to be seriously expensive to operate.
And yet, reddit which is much more complex, and of comparable reach (I don't have time to google the numbers right now, let's say it has 1/10 of the audience), costs much less than 1/10 of twitter's operational costs. And is profitable.
> There may well be a point at which it's simply economically infeasible to do it without splitting the expense into tiny slices borne by lots of different parties, the way we do for email.
Actually ... I suspect gmail can easily handle the entire world email infrastructure, cheaply and reliably. They already handle a two-digit percentage of the world email accounts.
For sure, facebook can do that - they already do it (although it is simplified email).
The reason email is sliced is not a problem of scale - it is a problem of control.
edit: removed half a sentence that was there, and which was written earlier.