If you ever pull up OpenStreetMap and notice that it has stale/bad data for an area, I now have firsthand experience with the knowledge of at least two reasons why:
1. The community includes the sort of people who'd rather have an incorrect map than an organized queue of issues that need to be addressed while working through them—the type of person for whom a thousand tickets marked "resolved" without the underlying issue being actually resolved is preferable because it gives a clean dashboard.
2. No effective response system when reporting disruptive users. (See #1.)
... then there's a third, too, which I actually already knew but had forgotten, which is that the tools for reviewing/diffing monstrous changesets are still very primitive. I can't stop the world to write something to fix it, but I suppose I could take the time to fix without the "stop the world part". Should I or anyone, though, for a community that's so uninterested in it?
@MichalBryxi I don't even think the main tools are necessarily *that* bad. I was def. impressed by how far along the in-browser editor has gotten. But it's stuff like: here's a user who has been observed to make subtly bad edits (e.g. >50% in all cases investigated). In the midst of a sprint that you've kicked off they come along and "help". Now you need to vet the deluge of (visual) edits changes they've just made, back out the bad, and keep the good. Good luck.
There are also cases like http://lists.openstreetmap.ch/pipermail/talk-ch/2023-March/011832.html where someone keeps doing unhelpful changes _at a large scale_. ISTM that OSM's anti-abuse mechanisms either are poor, or take no feedback.
