Steve Ivy and I have embarked on a prototype project to build a social network with its skin inside out. We’re calling it DiSo, or “Distributed Social Networking applications”. The emphasis here is on “distributed”.
The initial implementation of the project is built on WordPress, though making clear that this project is intended to be an example whose concepts should be able to be implemented on any platform. Since Steve offers a path to contribute to their effort (see “What’s Next”), I think the floater in my break list might just have found a permanent slot. With a twist and all for the better, so long as I find an area I can effectively contribute to.
I’ve tried to address related subjects on wp-hackers before, but the thread never picked up. The plugin paradigm is always a good approach, and if the implementation solidifies, code could ultimately make it into the WP core. +1 for that on my side! Just visit this very site with the excellent Operator FireFox add-on, and you’ll see what I mean. :-)
OpenSocial received a ton of hype when it was announced. Rumors of an early November launch surfaced following Arrington’s announcement of Maki Maki. The announcement turned out to be only that, an announcement. Soon after, I spoke with developers that suggested would open their platform by December 5th. That hasn’t happened either. Techcrunch has pointed to a Google group about OpenSocial in which a Google employee states “This puts us into January before the API is ready to be implemented by containers, so expect some early adopters to have a public launch early 2008.”
With so much activity at the standards/architecture level in the identity and social spheres right now, I’m one to say waiting a few months might actually be a very good thing for all involved parties here. A project of Dilo’s scale will thrive on the experimental angle and be malleable enough to rapidly adapt to changes, but OpenSocial is expected by many to be a stable platform to invest in, and has been presented (or represented) as so.