Ask HN: Open Social Network Systems
I'm currently building up a internet service that bears a lot of resemblance to the types of things you would see occur on social networking websites, though it itself is not supposed to truly be a social network.
I've been thinking a lot about REST lately, spurred on even moreso by a recent front-page article a man explaining REST to his wife, and I want to implement it in a way that creates a self-describing API with URLs, and is made as open as possible.
My current plans are, at first, not to reveal source code because I don't have a business model (so no plans to make revenue) and I would like some recognition for my team and I if my project is a true success.
However, I still want it to be as open as humanly possible, with all data theoretically machine-readable using the most popular open standards for declaring these objects etc.
This is where the Ask part comes in.. its very hard to look up all sorts of protocols and such for how to implement things, and through that REST article I was able to understand that implementing a separate API - albeit good for business - isn't the way the web is supposed to work.
What technologies should I use for data et al.
Current thoughts:
- Login & Registration (OpenID) - 'API' Access (OAuth) - Activity Feeds (RSS, ATOM, some open stream thing?) - Karma (???) - Comments (RSS???) - Profiles (??? RDF or something?) - Notifications (also RSS..?)
There's so much to think about when it comes to this, and I want my service to not just be a good - but one of the BEST citizens of the Open Web.
So Hacker News, what are your thoughts? What technologies are popular/easy to understand that will encourage openness and cross-communication the best?
Thank you so much.