[tahoe-dev] Free/Open alternatives to Dropbox

[Greg Troxel]

I think there are two separate problems:

  1) storing bits in the cloud

  2) having a local modifable copy of those bits when disconnected

tahoe solves (1) and does not address (2).

  One way to do that would be to write glue code to let Tahoe-LAFS serve
  as a "back end" in some of these schemes. DVCS-Autosync, in
  particular, was designed with git in mind but allegedly can use any
  distributed revision control tool for its back end. That would provide

I don't see tahoe as a distributed revision control scheme.  But one
could store the git repo used for syncing in tahoe.


I've generally been of the opinion that backup (certainly) and syncing
(maybe) belong above the filesystem so that they can be shared.
syncing only belongs in the filesystem when it's part of the
filesystem's fundamental concept of operations (like coda).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110514/7d08afba/attachment.pgp>