Build mechanism to catch invalid report causes

[denschub]

This is an idea that just came into my mind. It's nothing amazing, but I was not able to find a discussion on that yet!

We do see a certain type of reports on a regular basis, where users experience an issue that is completely out of our scope, and reporting them to us isn't doing anything good. One thing we could do to catch those kinds of reports and thus reduce the number of invalid issues that end up in our queue is to offer those "known-invalids" in the "What is wrong with the page at example.com?" step. If a reporter selects one of the known-out-of-scope reports, we could immediately stop the reporting flow and redirect them to the right place. Mainly, I'm thinking about

• "Site attempts phishing"
  • Redirect the user to https://safebrowsing.google.com/safebrowsing/report_phish/?tpl=mozilla
• "Site distributes malware"
  • Redirect the user to https://safebrowsing.google.com/safebrowsing/report_badware/
• "Site contains illegal contents"
  • Show a message that motivates the reporter to get in touch with their local authorities, because we can't handle those things.

There are probably a few other categories that would qualify here.

I don't think we have data on how many of those reports we actually get, so I'm not sure how great the value would be. However, that could be something to investigate, and it could also be something for a very motivated contributor or intern, because I think this could be great to have. :)

[ksy36]

Perhaps these could be inside an additional step after clicking on "Something else":

Instead of Briefly describe the issue: field, we could add one more step with these additional categories, and a link below them saying "None of the above". If a user clicks on it, they will be able to proceed to Briefly describe the issue: field.

There is another category that we can add, "Incorrect or inaccurate content", or something along these lines. In this case we'll show a message encouraging the reporter to get in touch with the author of the article, website owner, etc. As an example of such issue: https://github.com/webcompat/web-bugs-private/issues/39070