Hi, Ian Eure <i...@retrospec.tv> skribis:
> Is there some way for this code to be smarter about when it prints the > "report a bug" message, so it doesn’t tell users to report bugs when > none exist? Is there a way for it to notice that the problem is > related to networking, and tell the users to try again in a little > while? Is it worth removing the "report a bug" message entirely? > > It doesn’t feel great to tell users to report a bug for things that > aren’t bugs. They’re either closed, or never followed up on; it’s a > poor experience on both ends. I agree, it’s pretty bad. I’m fine removing the “report a bug” message, maybe replacing it with some clearer diagnostic and suggestion? WDYT? Thanks, Ludo’.
