SocialFS seeks to act as an open repository for your digital life, as well as a helpful bridge between the various services where that life currently resides. Of course, it's so much more. The beginnings of the vision is sketched out here.

Data portability is the ultimate goal: a Rosetta Stone for the web. The intermediate goals are all small pieces, loosely joined...

For people with data all over the place

• too many computers? running different operating systems? one home folder
• want one place to keep your social graph?

For Collaboration

• at its basest, a universal network share
• interfaces with collaboration tool APIs
• provides a platform for collaborative tools to use
• provides a home for collaborative applications to reside and be served from

For library developers wishing to write more generalized adapters to popular APIs

• the SocialFS data model should enable greater reuse

For web developers trying to write cool applications without caring about data persistence

• why can't the model of your MVC application be as portable as the application itself?

For open source developers trying to write cool applications

• Open source web applications can finally be accessible to the masses
• Desktop applications can piggyback on the great web app features

For web services trying to scale

• a SocialFS backend means a braindead interface to cloud infrastructure (Amazon, Google, etc.)
• or highly-customized database implementations (anything supported by SQLAlchemy)

SocialFS does not embody all of these projects. Rather it exposes the building blocks as an object-relational file system framework.