From 87e38b50239ef97c443152c5d737b7507bc17ffc Mon Sep 17 00:00:00 2001
From: Brad Fitzpatrick
Date: Wed, 12 Jun 2013 16:08:56 -0700
Subject: [PATCH] website: update uses
Change-Id: I06097eea55e7af394b299205bc404723b1eaf6a4
---
website/content/docs/uses | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/website/content/docs/uses b/website/content/docs/uses
index 6383fe9cb..6258f5cab 100644
--- a/website/content/docs/uses
+++ b/website/content/docs/uses
@@ -1,9 +1,10 @@
Use Cases
-Camlistore is currently more of a vision than a product, but let us
-at least lay out some of that vision here.
+First, read the overview.
-What could one potentially do with all this?
+These are some higher-level roadmap goals. Only the first few are
+done, but all are various stages of implementation (as of
+2013-06-12).
- Filesystem backups: easy initial use case. Since you can easily put files & directories and such in camlistore with camput, you can use Camlistore for your backups. Incremental backups are basically free.
@@ -18,5 +19,4 @@ at least lay out some of that vision here.
Import/export adapters for hosted web services: 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.
-