With luck, what they will be able to do by the end of the summer is build version 0.01 of core social network codebase and gain enough interest from open source developers for the project to keep rolling. With luck, over time the project will develop to the point that real social networks for casual people will be built upon it. With luck, those will gain traction.
These guys want to build Linux 0.01, you want "Linux On The Desktop". Not saying it is implausible, just quite different stages of product development.
What you really want is a central repository where your encrypted data can be uploaded to and only decrypted by those you choose (not the host itself).
I assure you the mechanics of how the data is stored is not of interest to 99% of people. Nobody really understands encryption anyway. Or is this site exclusively for geeks?
Obviously, no security is perfect, and given sufficiently evil central repository you'd still end up a situation of mistrust. But rather than take a chance with my private information simply because the people holding it tell me they aren't evil, I'll take responsibility for my own data and do my best as a user to make the right choices about how to treat that which I desire to keep private. If that means being picky about what I share/post, that's fine. If that means I need to run my own host and control access myself, well that's the burden I can choose to take to give me the peace of mind I'm looking for.
Additionally, if done right, the users do not need to know a whiff about encryption. I'll point to "https:// as a more successful example.
(Though HTTPS isn't exactly an unqualified success. Most people don't understand what it protects or notice when it isn't there.)
surely there is a great market share for ubiquitous encryption.
This way, the FB-alternative becomes a voice in the free market for respecting privacy.
If it's too geeky, it will never take off. It needs to be trendy and sassy, whether you like it or not. The "if we build it they will come" approach may shoot this thing in the foot.
On another note, are we putting data in control of the "user" or their "isp"?
This feels like the Kazaa or Napster of social networking, which can so easily be shut down by ISPs.
Lastly, people use Facebook at work and at home, and they log onto it from their friend's houses, their phones, etc. If it's all on my "node" at home, do I have to leave my stuff running all the time? That's not very convenient or green. And I don't want my bandwidth at home being eaten up every time my friends want to look at my vacation photos.
Anyway, kudos for the ambition, but the idea needs more time.