[OSM-talk] Responding to vandalism

James james2432 at gmail.com
Thu Mar 16 15:01:14 UTC 2017


Even if we had a Git pull request sort of mechanism, who would "approve"
edits? DWG? They are volunteers and wouldn't have time to validate the
millions of changesets that would come in. On the opposite end of the
spectrum, people could just flat out deny good edits which would make many
leave. Putting a restriction on "new" accounts is easily bypassable by
creating an account make a couple(30+ good changesets(very small)) wait a
couple days, then deface the map. The more restrictions you put, the
smarter people will get (just look at CAPTCHA, for bots, people would
upload images of captchas to a service which real people would solve and
return the answer to the bots). It's OPENStreetMap, not CLOSEDStreetMap

On Thu, Mar 16, 2017 at 10:48 AM, Clifford Snow <clifford at snowandsnow.us>
wrote:

>
> On Thu, Mar 16, 2017 at 6:47 AM, Manohar Erikipati <manohar at mapbox.com>
> wrote:
>
>> - 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 [3]
>
> - Auto-blocking known vandals to prevent repeated attacks [4]
>
> - 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 wiki [5]
>
> - 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 [6]. Building better support systems
>> to respond to bad edits could help more experienced mappers focus on
>> community building activities.
>
>
> Manohar,
> My experience is most of these edits can be cleaned up easily with simple
> edits. Some need full reverting, which can be done using JOSM, while others
> need careful pruning of the bad but leaving the good. I've fixed numerous
> pokemon edits in Washington State. I've only had to go to DWG 2or 3 time. I
> don't think we need to involve DWG in every case.
>
> I've send changeset comments and messages. Other than one belligerent
> individual who promised to report me if I kept reverting his phony edits,
> I've never heard back from any of them. There have been a number of example
> of appropriate changeset comments posted on talk and talk-us that let the
> mapper know the behavior isn't appreciated but also encourages them to
> become an active contributor. I suspect pokemon players could become
> prolific mappers.
>
> A tool that flags new parks, don't just look for named parks, but all
> parks - some of the players haven't gotten the word that it's only named
> parks, and new water features would be useful. Right now Ian Dees has a bot
> running on slack [1] and IRC[2] that picks up new users from the changeset
> feed. Sure it would be nice of someone could develop a similar bot to watch
> for new users adding pokemon features. But until we have that tool we
> really need to encourage more people to watch edits in their area.
>
> Best,
> Clifford
>
> [1] https://osmus.slack.com/messages/new-mappers
> [2]  irc://irc.oftc.net #osm-bot
>
>
>
>
>
>
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>


-- 
外に遊びに行こう!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20170316/36b0c3d9/attachment-0001.html>


More information about the talk mailing list