[tahoe-dev] barriers to using tahoe

[Chris Palmer]

Jody Harris writes:

> You use bookmarks because you understand that the system does not offer
> you another way of keeping track of files created through the WUI. As a
> new initiate to Tahoe, I am viewing Tahoe as a file repository. I put

My plan for Octavia is to provide only a filesystem interface (first with
FUSE, then hopefully with proper filesystem drivers, prioritizing Windows).
I think Tahoe-LAFS should do the same, because once you have a regular
filesystem, all the other interfaces (FTP, WUI, ...) fall into place
naturally given existing software. Your WebDAV server might not even need to
know its underlying filesystem is Tahoe-LAFS (or Octavia :)).

My precious few drunken vacation hours go into my 10 other projects, but if
I were a Tahoe developer, I'd drop everything and go nuts on developing for
FUSE.

> For most users, bookmarks are a work-around (for something they will see
> as badly broken), not an interface.

Exactly -- bookmarks were a kludge around the unusability of URLs.
Cryptographic URLs are that much less usable.

> >  >  - Using the CLI is arcane, mysterious and cryptic.

I certainly disagree, but then, I am a Unix pervert. Not that Octavia's CLI
is minimally acceptable at the moment. Regardless, a filesystem interface
obviates the problem.