3 ms·
Some thoughts on this: - There's already a click-based interaction mechanism, the "flag" link. That's non-specific ("here be problems"), but also means that a
by dredmorbius 3y ago
Some thoughts on this:
- There's already a click-based interaction mechanism, the "flag" link. That's non-specific ("here be problems"), but also means that any type of issue can be reported with only a single mechanism and reporting flow.
- Yes, a more complex workflow for issue reporting could be constructed. Those ... tend to be complicated, not be especially useful, often omit the specific concern the reporter has in mind, and if overly arduous, result in people simply selecting the first option and moving on. Such systems can also become ossified and/or brittle over time, where an email-based system is inherently flexible and adaptable.
- Reporting links can also be abused by bots, web scrapers, and the rest, which means limiting them to registered members, and perhaps a subset of those (as is the case with HN's "flag" link). Email is the Universal Reporting Mechanism as I've noted in another comment on this thread.
- Email is sufficiently non-structured to address a wide range of issues. The one standardisation I've been asked to provide is to include the specific item ID in the subject of the email. This lets mods pull up the item directly using macros written for that purpose. I suspect that often the issue is reasonably apparent on doing so.
- I make extreme efforts to keep my standard-issue emails brief, clearly identify the post and source link, and suggest a remedy, all in consideration of moderator time. I suspect many other frequent reporters do likewise. Mods do respond typically within an hour to a day, and will often fix issues well before responding.