Rooba
/
perkeep
mirror of https://github.com/perkeep/perkeep.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc tweaks for website

This commit is contained in:
Brett Slatkin 2011-01-29 13:37:22 -06:00
parent 400e437905
commit 9c2ebaeb47
3 changed files with 20 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/content/docs/status
View File

@ -25,9 +25,9 @@ pieces and use cases, and where they're at.</p>
<tr><td>Search / indexer server</td><td>5%</td><td>Toy prototype started. See <a href="/gw/indexing/basic">indexing/basic</a>. Upcoming area of focus.</td></tr>
<tr><td>JSON signing / verification server (Go)</td><td>80%</td><td>See <a href="/gw/server/go/sigserver">server/go/sigserver</a>. Does JSON signing and verification, but doesn't yet permit uploading keys. This isn't a formal part of Camlistore but is rather a temporary bootstrapping component, a crutch for JavaScript.</td></tr>
<tr><td>JSON signing / verification server (Go)</td><td>80%</td><td>See <a href="/gw/server/go/sigserver">server/go/sigserver</a>. Does JSON signing and verification, but doesn't yet permit uploading keys. This isn't a formal part of Camlistore but is rather a temporary bootstrapping component, a crutch for JavaScript/simple clients.</td></tr>
<tr><td>JSON signing / verification server (App Engine)</td><td>70%</td><td>See <a href="/gw/server/appengine/sigserver">server/appengine/sigserver</a>. Does JSON signing and verification, but doesn't yet permit uploading keys. This isn't a formal part of Camlistore but is rather a temporary bootstrapping component, a crutch for JavaScript.</td></tr>
<tr><td>JSON signing / verification server (App Engine)</td><td>40%</td><td>See <a href="/gw/server/appengine/sigserver">server/appengine/sigserver</a>. Does JSON verification, but kind of broken. This isn't a formal part of Camlistore but is rather a temporary bootstrapping component, a crutch for JavaScript/simple clients.</td></tr>
</table>
@ -49,7 +49,9 @@ time.</td></tr>
<tr><td><a href="/gw/clients/chrome/clip-it-good">Clip It Good</a></td><td>80%</td>
<td>Camli port of <a href="https://chrome.google.com/extensions/detail/aimbcenmfmipmcllpgajennfdfmmhmjj">Clip It Good</a>. (currently still forked)</td></tr>
<td>Camli port of <a href="https://chrome.google.com/extensions/detail/aimbcenmfmipmcllpgajennfdfmmhmjj">Clip It Good</a>. Chrome extension allows right-click on images and save them to your blobserver. (currently still forked)</td></tr>
<tr><td><a href="/gw/clients/python">camliclient.py</a></td><td>50%</td><td>example command-line tool for uploading/downloading files using the <a href="/gw/lib/python">Python library</a>.</td></tr>
</table>

4
website/content/docs/uses
View File

@ -8,13 +8,13 @@ at least lay out some of that vision here.</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.</li>
<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</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>

18
website/content/index.html
View File

@ -8,18 +8,26 @@
<li>an acronym for <i>"Content-Addressable Multi-Layer Indexed Storage"</i>, hinting that Camlistore is about:
<ul>
<li>content-addressable storage</li>
<li>separate interoperable parts (storage, sync, sharing,
modeling), with well-defined protocols and roles</li>
<li>separate interoperable parts (<a href="/docs/arch">storage</a>, <a href="/docs/terms#graphsync">sync</a>, <a href="/docs/sharing">sharing</a>,
<a href="/docs/schema">modeling</a>), with well-defined protocols and roles</li>
</ul></li>
<li>your "home directory for the web"</li>
<li>pro-JSON (yet aggressively format agnostic)</li>
<li>pro-GnuPG (for <a href="/docs/json-signing">signing claims</a>)</li>
<li>pro-OpenPGP (for <a href="/docs/json-signing">signing claims</a>)</li>
<li>pro-paranoia and privacy</li>
<li><a href="/docs/uses">ambitious</a>, but ...</li>
<li>simple!</li>
<li>programning language-agnostic (parts and different implementations in <a href="http://golang.org/">Go</a>, Python, Java, Perl, Bash, ... the language doesn't matter.) What matters is well-defined, simple HTTP interfaces.</li>
<li>programming language-agnostic (parts and different implementations in <a href="http://golang.org/">Go</a>, Python, Java, Perl, Bash, ... the language doesn't matter.) What matters is well-defined, simple HTTP interfaces.</li>
<li>neither "Cloud" nor "Local". happily both.</li>
<li>a "20% project" from a few Google employees, but not Google-centric nor endorsed by Google (other than them letting us open source our side project)</li>
<li>not yet ready for users</li>
<li>ready for developers (at least those without strong <a href="http://bikeshed.org/">color preferences</a>)</li>
</ul>
<p>but, is...</p>
<ul>
<li style="margin-top: 1em">not yet ready for users</li>
<li>not a typical peer-to-peer system or DHT</li>
<li>not (yet?) a "MySQL alternative"</li>
<li>not necessarily a product in itself (e.g., not Drupal)</li>
<li>not necessarily a replacement for S3-like storage</li>
</ul>