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

[tahoe-lafs]

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

Comment (by davidsarah):

 Replying to [comment:22 warner]:
 > * marking the files as prohibited on the directory listing is a nice
 >   touch, but I'd be happy to see this feature go in without it. Also, by
 >   removing the More Info link, it's harder for users to find the blocked
 >   filecap (and in particular the storage-index), so they can edit their
 >   {{{access.blacklist}}} file to unblock the file later.

 I added the reason in that column because the More Info page ended up
 giving
 an error, and there was no point in having the link in that case. I'll
 have a
 look at how to get the info page working and showing the blacklist reason.

 >   Maybe we could put "Access Prohibited" in the info column and make it
 a
 >   link to the same old More Info page as before, then add the reason to
 the
 >   more-info page? Likewise, I don't think we need to change the "type"
 >   column to indicate the file has been blacklisted: the strikethrough is
 >   plenty big enough.

 I agree. The change to the type column was there more because it was
 slightly
 easier to implement than showing the original type code (and because I
 didn't
 have the "Access Prohibited" at that point), than because it's necessary.

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