Social networks have taken a few of the biggest distributed applications of the web and started mass producing them, in watered down form. But notice how they have to keep absorbing every new fad that comes along? The coup will start with some platform that allows ideas to be realized faster than the networks can clone them.
Search is not easily distributable and will remain silo'ed up for a long time.
GMail is huge. But SMTP is still a distributed protocol, you can switch providers in a blink and not lose anything other than a shiny interface.
NNTP was always run in a hierarchical fashion and more importantly is centered around discussion groups. People a) prefer more control over their publishing/group-comm (blogs, forums) and b) demand the "follow individual" pattern (RSS).
Consequently the Usenet-monolith shattered into said services, all of which you can either run on your own server, or rent from a service-provider.
Sharing always sucked and that is the niche (apart from the social graph) that made Facebook big. However, today we can build mashups that plug into all these services and present them under a unified interface - just as pretty as facebook.
The only missing bit to lace it all together is the social graph. Today our little mashup has to load the graph from either facebook, twitter or google.
In the future some smart kid will come up with a "DNS[1] for social relations" and everyone will start using that, just because it's the natural thing to do and because futzing with proprietary API-keys is so 2011.
[1] As in Domain Name System
I think you may underestimate the importance of the shiny interface. Regardless, the use of an outside provider is still a move toward centralization. Ten years ago, the small offices I did software work in all had local email servers. Today, running an email server well is a big job, and those offices all outsource their email service to much larger companies.
People ... demand the "follow individual" pattern (RSS) ... In the future some smart kid will come up with a "DNS for social relations"
It's interesting that you bring up RSS. I was thinking about that too. I think RSS is already very nearly a "DNS for social relations." But it's also failed to catch on outside the circle of techies, early adopters, and web-potatoes.
I'd say the failure of RSS to achieve mainstream popularity is an example of a decentralized system losing out to centralized alternatives. Like Facebook. Facebook is just plain simpler to get started with than a self-administered approach like RSS or a hypothetical next-generation DNSfSR would be. And Facebook and Twitter both killed off their RSS feeds once they'd felt they'd achieved a certain critical mass. They understand that RSS is an alternative for much of what they do.
I don't celebrate any of this. I use and like RSS. I wish I didn't feel the need for a Facebook account (but that's where my real-world friends are). But the pattern I see is that convenience beats out control every time. For complicated devices like computers and for complicated situations like the (real, human) social network, the inevitable complexity that comes along with local, personal control is often a problem, not a feature.
Under such circumstances, I don't see how Facebook (or its successor) will be overtaken by a distributed anything.
Faroo seem to be doing a pretty good job, although their UI could do with some love.
http://www.google.com/apps/intl/en/customers/ says you are wrong.
And I don't think that's a bad thing - Facebook is a problem, not Google. Don't tar every company with the same brush.
It's just foolish to give up control of one of the most important communication resources your business has to a company with a notoriously poor customer service record.
http://www.formortals.com/gmail-is-not-a-business-tool-perio...
Regardless, that seems like a move toward central control rather than toward anything I'd describe as a distributed service.
I think the issue is that there is difference between allowing people to log into an account with Facebook and companies actually sharing their data with each other. There's also the reality that as companies die, merge or change course, the massive amounts of data they have often simply becomes unused.
Reminds me of the joke about there being two kinds of people in the world; those who have lost data, and those who will.
The second is that you are turning over all of your internal communication, almost all of which should never leave the company, to a third party.
I'm not sure I understand this. Why isn't Google in the business of making sure its paying customers stay in business?
> The second is that you are turning over all of your internal communication, almost all of which should never leave the company, to a third party.
How is this any different from storing source code on GitHub, or using Campfire to communicate?
A very reasonable argument is that you shouldn't be using those either. GitHub is fine for open source projects but if I were involved in writing proprietary code I'd probably not put it up there.
It's also hard to talk percentages -- there are a lot more companies storing source code on private servers than using external hosting. So yes, more stories of that, but it's hard to talk percentage chance rather than absolute numbers.
Where does one draw the line?
There were once many search engines, now there is Google. Usenet was a distributed system; now there are centralized forums. Email was once something that was largely administered locally, now everyone has a Gmail account. Sharing things with friends and family used to be done through a constellation of different services, like blogs and Flickr and email. Now Facebook does all of those things.