-
I applaud your plea for people to take control of their data and strongly agree in principle. However, there are a couple of problems:
- In some cases, the available open source, self-hosted solutions simply suck incredibly badly compared to the commercial hosted solutions. Examples include rnews, which is awful compared to Google reader and I can’t seriously believe that you would recommend Posh over Netvibes, iGoogle, etc. at this point. Much as I really want to like this software, it is a bit like asking a windows user to convert to linux in 1992. A good idea in principle, but it’s not going to happen for the average user until the software has comparable features and is as easy to use.
- In the case of social networking sites there are network effects to consider. For example, bookmarking sites like del.icio.us and digg get better the more people that use them and the more friends that you have on them. Increasingly, almost all web 2.0 services have some sort of friends or recommendation system (of varying utility) that relies on a large number of users for it to work well. At the moment, you cannot reproduce this by installing something on your own webhost.
What I would recommend doing at the moment is to find a way to backup as much of your web presence as possible, just as you would with files on your own computer. With RSS readers this simply means keeping a copy of your opml file, but for other services it is not so simple. I believe that installing sweetcron might do some of the work for you, since I think it works by downloading the data from your feeds to a local mysql database on your webhost. However, I haven’t looked into the code and the documentation is not good enough for me to be able to tell if it really stores everything permanently. Definitely a good idea in principle though.
In the long run, I think we need to push for the idea that social services should work more like email than like websites so that no single company is in control of our data. By this I mean that you would have a “social server” based at your work, ISP, webhost or even your home, just like you have with an email server. These servers would talk to each other in a common language, pushing friend statuses, articles, bookmarks, ‘tweets’, photos, videos, etc. to each other based on who you are following and various recommendation algorithms. Initially, this would have to work with the APIs of existing services so that you don’t lose your network by switching to the new system. Some of the popular services that are quite closed (e.g. Facebook) are going to cause problems with this, so we need to push for services to have APIs that are as open as possible as a first step.
-
Pligg? IMHO, I’d choose it’s fork http://socialwebcms.com/
Worth are read Social CMS Buzz:
http://tinyurl.com/bvzy7g
Comments are now closed.


7 comments