As it currently stands, if something goes wrong with Gridsync and/or Tahoe-LAFS, it can be difficult for end-users and developers to determine why: the recommended debugging process involves having a user re-run the application with the --debug flag in hopes that a) they might be able to reproduce the issue a second time and b) that the logs will provide enough information to the developers to get a sense of what went wrong and how/why. Unfortunately, at the present moment, logging systems in both Gridsync and Tahoe-LAFS are rather poor (providing either too little information or too much) and, although there are plans to ameliorate this in the future, asking users to drop down to a terminal to manually collect logs via the command line arguably constitutes an unnecessary burden for everyone.

Accordingly, it would be nice if this was improved; a user-facing option/action should be provided somewhere within the GUI (perhaps under the "Help" systray menu action) that would allow users to easily and retroactively export debugging/logging information to developers in the event that something goes wrong. In addition, users should have the ability to review the information before exporting it (which, ideally -- and in conjunction with #61 -- should contain little to no identifying information to begin with).