[OSM-talk] Responding to vandalism
manohar at mapbox.com
Thu Mar 16 13:47:25 UTC 2017
Last saturday, Central park in New York City was vandalized by a new
OSM user `Meowthreetimes` in all the map edits:
- 46756622 introduced a fictional lake inside Central park
- 46756461 renamed Central park in
- 46756506 introduced a fictional lake near Fort worth Dallas
It took 2 days for the edits to be noticed and reverted on one of the
most popular locations in the world.
This was possibly preventable with a more active mapping community,
but a previous incident  highlights how simple cases like dragged
ways can stay around the map for months under the eyes of local
mappers. The current strategy of leaving changeset comments to users
to prevent bad edits does not scale, especially if the mappers do not
read messages like Maps.me editors , or if there are no expert
mappers in the area who are knowledgeable in reporting and reverting
Thinking out loud on how we could better improve the current process
to act on bad edits:
- DWG currently acts promptly on incidents reported via email, but we
need a more accessible mechanism that allows new users to report such
incidents directly from the website or editors. The email details and
existence of DWG, is only available currently in the wiki 
- Auto-blocking known vandals to prevent repeated attacks 
- An organised repository to report and learn from previous attacks.
There seems to have been an effort to do this many years ago on the
- More visibility, awareness of QA tools and history tab on the OSM
homepage. Most of the really powerful QA tools like osmhv and osmose
are only known to advanced users.
It would be great to hear more approaches that could protect the map
against common mistakes and intentional attacks. Much of the world
lacks an active mapping community, so it is up to a small set of power
mappers to catch and revert most of the bad edits . Building better
support systems to respond to bad edits could help more experienced
mappers focus on community building activities.
osm : manoharuss
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk