An adjacent 5-page thread
Challenger3802 wrote:we definitely need something to stop general errors being reported, then the reporter vanishes into the ether, never to be heard from again. Those that do reply are generally heavy users and get back within two days, most though after 2 days can't remember where they were when they submitted the report, and also can't remember why.
discusses this notion in detail. Agreement centered around the idea of somehow forcing reporters to add a description to a "general error" map issue, probably by sending an automated request that the reporter can fill in when they stop. The UR would not appear until the reporter completes that step. Another idea was to eliminate the driver "first map issue" point bonus. But both of these have to be done by Waze.
Using the great Chrome extension URO+ combined with a personal wiki to hold my favorite boilerplate responses, I have found it goes pretty quick to send canned queries to all the general-error URs with no descriptive text. I'm accustomed now to the depressing fact that maybe 5% of them will respond, but since it's so little effort to send the queries using URO+ and boilerplate, I don't care so much anymore.