These series of guest posts are written by the teams attending the Tetuan Valley Startup School 2012 Spring Edition. This post is from the Fandomain team (@), formed by Carmen Bermejo.
Half of the entrepreneurs I’ve met in the last two months told me that their project consist on a social network. It reminds me of ten years ago when everybody wanted to launch a web portal.
But this is just a more dynamic way to organize and create content. If your idea is really trying to cover a necessity and not just following the trend, that’s fine.
Where is the problem? Big established social networks (and I’m not looking to anyone) has set a very bad example to follow. If you are doing this, there are a couple of things you should consider:
Open software: Are you sure you want to reinvent the wheel?
Ok, you have an awesome idea for a social network. Perfect. But that doesn’t mean that you have to program all from scratch. There are a lot of previous work done that you can use so you can center your efforts on the really innovative aspects of your idea.
Also if you use open software that will aloud your users to collaborate, fixing bugs or creating new features. That will also have the benefit that they’ll consider your social network something of their own and helps you to build the sense of community that it’s one of the most important things a social site needs to succeed.
Cons: If you have some very secret implementation that you don’t want anybody to copy or your end goal it’s to sell your site/software to a big company.
Examples:
- Diaspora Software written on Ruby on Rails.
- Elgg Software written on PHP.
- Apache Wave (previously Google Wave). A protect Google gave away to the community after they decided to focus on Google plus. Written with GWT (Google Web Toolkit).
Federation/OpenID: Sharing only with yourself is not sharing.
When you say that you want to build a social network one of the main problems people thinks are: “Register on another site, no thanks.”. Well, in case you didn’t knew, Internet wasn’t suppose to work like that.
What I’m talking about? Think how email works. You have an account on a server/email provider, like for example gmail or hotmail or even your own server and you can use it to communicate with anyone that have an email account on any server on Internet, it doesn’t matter where.
But social networks can’t be like that right? That’s where popular belief it’s wrong. Not only it’s possible, there are in fact a lot of social networks and initiatives that works exactly like that.
You have an account on a social network that is in a server and is managed by someone: a company, a free software foundation, a group of friends or even you on your own server. And you can use that account to share content and communicate with anyone that is in a “compatible” social network. That usually means that it’s another social network based in the same software but in other server, but there are some protects and initiatives that aims to create protocols and standards so social networks build with different software could communicate.
So if this is possible, why doesn’t everybody does that? For big social networks, having the monopolio goes on their advantage. It doesn’t matter if what they offer it’s better than smaller social networks or not, because they have the users and if you want to communicate with them you need an account on their system. That works for them, but remember, you are not Facebook.
For more information about this projects:
- Open-id for open and shared login that use OAuth.
- OpenSocial: A set of specifications and APIs (including OAuth).
- Diaspora: Based on Diaspora Software
- Lorea (N-1): Based on Elgg Software, but their objective it’s to aloud heterogeneous social networks (made with different software) to connect.
- Kune: Based on Apache Wave. They aim to make open software social networks user friendly.
- GNU Social: The GNU initiative. As long as I know it’s only an alternative to Twitter.
- Identi.ca: Another alternative to Twitter.



