[tahoe-lafs-trac-stream] [tahoe-lafs] #1425: blacklist support

[tahoe-lafs]

#1425: blacklist support
-----------------------------------+-------------------------------------
     Reporter:  warner             |      Owner:  warner
         Type:  enhancement        |     Status:  closed
     Priority:  major              |  Milestone:  1.9.0
    Component:  code-frontend-web  |    Version:  1.8.2
   Resolution:  fixed              |   Keywords:  blacklist review-needed
Launchpad Bug:                     |
-----------------------------------+-------------------------------------

Comment (by zooko):

 When releasing 1.9, we should go to extra effort to communicate what this
 change does and doesn't do. I've been learning that almost all users have
 very simpleminded models of things, for example I think the existence of
 the public web gateway made most users think that Tahoe-LAFS was nothing
 more than some sort of online service. Explaining this feature (in the
 NEWS/release-notes/etc.) may be a good opportunity to explain the
 difference between running your own software (Tahoe-LAFS storage client)
 to upload or download files vs. visiting a web server (Tahoe-LAFS gateway)
 operated by someone else and asking them to serve files to you.

 This feature lets the operator of a Tahoe-LAFS storage client (== Tahoe-
 LAFS gateway == the web server in question) configure their software so it
 refuses to serve certain files (to anyone). It does not give them any
 ability to affect whether ''other'' Tahoe-LAFS storage clients/gateways
 access those files.

 How can we make this clear? Maybe the only way to make this clear is to
 create a variant of http://tahoe-lafs.org/~zooko/network-and-reliance-
 topology.png which shows multiple gateways in use, and indicate on that
 diagram that the blacklisting feature affects only the single gateway that
 chooses to use it.

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