[tahoe-dev] [mm] Fwd: Tahoe

[Brian Warner]

> > Surprised. I'd've thought the CLI was more used!
> 
> It's early days.  What Unix hackers *really* want, I think, is a FUSE  
> interface, of which there are three preliminary ones contributed so far.

Actually, what I realized over the weekend that *I* really want, is a 'tahoe
put -r' that will properly avoid duplicate uploads, which I can run from a
cron job over my whole home directory. That would handle my personal backup
needs just fine.

All of our CLI commands currently use blocking httplib calls to the webapi
service on a local or remote tahoe node. We could conceivably implement 'put
-r' this way, but I'm concerned that it would be rather slow with a local
node (since it would have to push your whole filesystem over loopback HTTP,
store each file in /tmp/ one at a time, hash it, then discover that it's
already present in the grid). (of course, using a remote node for this would
be unbearably slow).

So I'm considering expanding the 'control.furl' interface to provide 'put -r'
and 'get -r' functionality to the local filesystem. The 'tahoe put' CLI
command could require that ~/.tahoe/private/control.furl exists. Or, it could
use control.furl if present and fall back to doing a bazillion webapi calls
if not.

Authority-wise, anyone you give private/control.furl to will be able to read
and write any file that the tahoe node can get to, so it really is private.

cheers,
 -Brian