[tahoe-lafs-trac-stream] [tahoe-lafs] #1487: remove the notion of "rootcap" from FTP-and-SFTP.rst

[tahoe-lafs]

#1487: remove the notion of "rootcap" from FTP-and-SFTP.rst
-----------------------------+--------------------------------
     Reporter:  zooko        |      Owner:  nobody
         Type:  enhancement  |     Status:  new
     Priority:  major        |  Milestone:  undecided
    Component:  unknown      |    Version:  1.8.2
   Resolution:               |   Keywords:  docs usability ftp
Launchpad Bug:               |
-----------------------------+--------------------------------

Comment (by zooko):

 Perhaps there are other contexts where the notion of a rootcap is more
 salient, but in [source:docs/frontends/FTP-and-SFTP.rst], I'm not sure if
 it adds anything over "dir cap". The two users that I spoke to both were
 setting up FTP (or SFTP), and both were stymied by thinking that they
 couldn't use any old dir cap, they needed to get a special "root" cap, and
 didn't know where to get one or what was special about it. The thing is:
 there ''isn't'' anything special about it in the context of
 [source:docs/frontends/FTP-and-SFTP.rst], is there? Any dir cap that you
 put in there is automatically what we call a "rootcap" isn't it? Or do I
 misunderstand the meaning of "rootcap"?

 Or is the idea is that you should have only a single root cap that you use
 for all of your Tahoe-LAFS access, such as in your web browser bookmarks
 you should have a single entry for the root to all your Tahoe-LAFS
 resources, and when configuring your SFTP server you ought to put in the
 same root cap for it as you have in your bookmarks? I don't agree with
 that idea.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1487#comment:2>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage