Why SocialFS?
If you read through this whole screed, you may still be left wondering: why the name SocialFS?
The answer is twofold: first, I needed a final project for my Social Computing class, and revisiting these ideas seems like a worthwhile endeavor. But the second, deeper answer is what I think is missing from my prior post. In my zeal to explain polymorphic file types and mixins and all, I forgot to even hint at the primary inspiration. I completely neglected to point my big ol’ middle finger at Facebook, the Social platform — for now — and public № 2 when it comes to data portability (you have to give the top spot to Microsoft, especially after it so brazenly corrupted the ISO: bravo, guys!).
In spite of how boring data portability may seem to the nongeeks, the skeptics, and especially to the social network socialites — it’s kinda, like, a big deal (just ask any Hotmail user). Lip service and APIs aren’t enough, especially with constrictive terms of service.
So yes, Scoble, if you’re looking for a place to keep your social graph, why not on your own servers in a SocialFS instance?
(I guess I have to write it first.)
May 6th, 2008 at 4:29 pm