[tahoe-lafs-trac-stream] [tahoe-lafs] #1941: when an upload or check fails, link to a full explanation of what happened

[tahoe-lafs]

#1941: when an upload or check fails, link to a full explanation of what happened
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  daira
         Type:  defect   |     Status:  assigned
     Priority:  normal   |  Milestone:  1.11.0
    Component:  code-    |    Version:  1.9.2
  network                |   Keywords:  usability upload transparency
   Resolution:           |  ostrom
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by kpreid):

 This is my UI design opinion:

 The very most fundamental thing that needs to be done is that the error
 should be formatted for the web, not as a Python traceback. Tracebacks are
 for when ''the program itself does not understand what went wrong,'' which
 is not the case here.

 This is a random idea I had which Zooko liked:

 The error page should prominently contain a bar graph, which contains the
 same information as the current error, but in a graphical and explained
 format. For example:

 {{{
 You have this many storage servers online: ###......
 You need this many to upload this file:    \---/
 }}}

 An actual graphical rather than ASCII-art version would have the
 resolution to distinguish between needed and happy, and storage servers
 which are full vs. offline. Furthermore, each box could be labeled with
 the storage server's name, perhaps turned sideways (or perhaps turn the
 entire graph sideways).

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1941#comment:7>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage