perkeep/website/content/docs/uses

<h1>Use Cases</h1>

<p>Camlistore is currently more of a vision than a product, but let us
at least lay out some of that vision here.</p>

<p>What could one potentially do with all this?</p>

<ul class='lispaced'>
<li><b>Filesystem backups</b>: easy initial use case.  Since you can easily put <a href="/docs/schema">files & directories and such</a> in camlistore with <a href="/cmd/camput">camput</a>, you can use Camlistore for your backups.  Incremental backups are basically free.</lil>

<li><b>Efficient remote filesystem</b>: should be easy to do an aggressively caching remote FUSE filesystem.  Read-only is trivial.  Read-write shouldn't be too painful. Every modification would be snapshotted implicitly, so revision control would be the default.</li>

<li><b>Decentralized sharing system</b>: share anything of yours with anybody or everybody (private is the default).  This is already starting to work.  See <a href="/docs/sharing">sharing</a>.</li>

<li><b>Blog / photo hosting / Document Management CMS:</b>  I intend to run my personal blog and photo / gallery hosting (with permissions) off of Camlistore.  I also intend to replace my "scanningcabinet" document management software and use Camlistore instead.</li>

<li><b>Decentralized social networking</b>: a lofty but persistent goal. For example, to implement comments or tagging: One person could use claims to attach metadata to another person's image blob. The signing lets you verify identity. The sharing/syncing semantics of camlistore let you easily save a copy of all your friends' pictures.</li>

<li><b>Import/export adapters for hosted web services:</b>  Don't worry about web services shutting down or going downhill.  Mirror all your data online in your private store.  Create it either in Camlistore (using open tools) and export to hosted services, or create content in hosted services and continually mirror it back into your private Camlistore.  Relax knowing that your data is yours, forever.</li>


</ul>