Re: [OSM-talk-be] talk: "responding to vandalism"

2017-03-21 Thread Jonathan Beliën 

Hi guys,

I like the idea to validate edits coming from certain sources (Maps.me, 
...).


But even though there is some vandalism (aaah those PokemonGo players) 
and do not think we should validate everything and everyone (and that's 
ok if we miss some of that vandalism).
An important part of OSM strength is that freedom and that anyone can 
contribute directly ! I think we need to keep that strength.


That said, I'm a PHP/PostgreSQL developer and I already own a server 
dedicated to OSMBE (Tasking Manager [1], brand new registration form 
[2], ...) and I would be happy to try that lituanian tool (and why not 
contribute to improve it).


Good afternoon !

[1] : http://tasks.osm.be/
[2] : https://members.osm.be/

Jonathan


Le 19-03-17 à 22:33, joost schouppe a écrit :
Usually, I feel like Karel does. It is not really urgent to work on 
this, as it is not so very common. Still, there is some work to do: 
lots of newbie mistakes, the very occasional random vandal, sometimes 
damaging maps.me  mistakes, misguided Pokémon Go 
players.


Most of that work is getting done anyway, but sometimes we do miss 
things. It would be nice to have it a bit more structured.  Maybe that 
might lighten the load for those that are doing it now. The most 
important thing: it might help us prepare if ever bigger problems arise.




___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be


___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] talk: "responding to vandalism"

2017-03-19 Thread joost schouppe 
Usually, I feel like Karel does. It is not really urgent to work on this,
as it is not so very common. Still, there is some work to do: lots of
newbie mistakes, the very occasional random vandal, sometimes damaging
maps.me mistakes, misguided Pokémon Go players.

Most of that work is getting done anyway, but sometimes we do miss things.
It would be nice to have it a bit more structured.  Maybe that might
lighten the load for those that are doing it now. The most important thing:
it might help us prepare if ever bigger problems arise.
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] talk: "responding to vandalism"

2017-03-19 Thread Yves bxl-forever 
The idea is interesting.  Wikipedia uses a similar process: edits by anonymous 
or new users are flagged as potentially suspicious, and users can validate 
contributions by other users.

I understand Karel’s concern: perhaps that there isn’t much *vandalism* in OSM 
in Belgium so far.
But the problem may be that newbie-friendly apps—such as MAPS.ME or 
Wheelmap—encourage lots of new people to add data to OSM without having to 
learn the data model or how to check whether that data is already existing.  I 
often remove duplicate nodes, fix tags or fix location of objects created by 
users of those apps.  The more newcomers, the more we’ll have to deal with 
incorrect data.  These people certainly have good intentions but having a 
process to validate potentially incorrect changes will be necessary as the 
community grows.  And that will work for deliberate vandalism too.

Cheers.
Yves



On Sun, 19 Mar 2017 19:19:39 +
Karel Adams  wrote:

> What's urgent or important about this? Is vandalism an issue on OSM? A 
> problematic issue? I have as yet not seen any.
> 
> 
> 
> On 19/03/17 17:20, Ben Abelshausen wrote:
> > This is an excellent idea, perhaps we should discuss this the next 
> > hackday? Or can someone try and set this up for Belgium?
> >
> > Met vriendelijke groeten,
> > Best regards,
> >
> > Ben Abelshausen
> >
> > On Sun, Mar 19, 2017 at 6:07 PM, joost schouppe 
> > > wrote:
> >
> > Hi,
> >
> > There is an interesting thread going on in the talk mailing list:
> >
> > https://lists.openstreetmap.org/pipermail/talk/2017-March/077672.html
> > 
> >
> > It started of with some complaining about vandalism, but it got
> > interesting when Thomas Straupis started explaining how they work
> > in Lithaunia. Basically, ALL changesets are validated. But
> > changesets by "known mappers" are automatically approved, and some
> > changesets are highlighted because they are marked by other tools
> > as "suspicious".
> > (this is the same Thomas I interviewed recently about their
> > dataconflation strategies:
> > http://www.openstreetmap.org/user/joost%20schouppe/diary/40605
> > )
> >
> > With Zors already checking all new mappers' changesets using the
> > welcome tool (thank you!), it might be interesting to see if we
> > can expand on that here too.
> >
> > Here's some practical stuff from his e-mail:
> >  
> > > Is your process documented anywhere and is the code available?  
> >
> >   There is a "help" page, but it is in Lithuanian... Maybe google
> > translate can help:
> > http://patrulis.openmap.lt/pagalba.html
> > 
> >
> >   Code (php+postgresql) is very basic and dirty (i'm not a web
> > developer) and I didn't have time to put it on github yet (planning to
> > do that for a year or so...). But code is also full of Lithuanian
> > comments and names...
> >
> >   If somebody wants to have a look at it - I can share/send the code
> > and give any information required in English.
> >
> > P.S. This patrolling stuff is integrated with QA tools (fetching a
> > list of errors from keepright, osmose as well as doing local error
> > checking) and data synchronisation tools. So "all in one" solution.
> > You get a list of unapproved changes, a list of not yet fixed errors
> > and a status of synchronisation of different items.
> >
> > -- 
> > Joost Schouppe
> > OpenStreetMap
> >  | Twitter
> >  | LinkedIn
> >  | Meetup
> > 
> >
> > ___
> > Talk-be mailing list
> > Talk-be@openstreetmap.org 
> > https://lists.openstreetmap.org/listinfo/talk-be
> > 
> >
> >
> >
> >
> > ___
> > Talk-be mailing list
> > Talk-be@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-be  
> 

___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] talk: "responding to vandalism"

2017-03-19 Thread Karel Adams 
What's urgent or important about this? Is vandalism an issue on OSM? A 
problematic issue? I have as yet not seen any.




On 19/03/17 17:20, Ben Abelshausen wrote:
This is an excellent idea, perhaps we should discuss this the next 
hackday? Or can someone try and set this up for Belgium?


Met vriendelijke groeten,
Best regards,

Ben Abelshausen

On Sun, Mar 19, 2017 at 6:07 PM, joost schouppe 
> wrote:


Hi,

There is an interesting thread going on in the talk mailing list:

https://lists.openstreetmap.org/pipermail/talk/2017-March/077672.html


It started of with some complaining about vandalism, but it got
interesting when Thomas Straupis started explaining how they work
in Lithaunia. Basically, ALL changesets are validated. But
changesets by "known mappers" are automatically approved, and some
changesets are highlighted because they are marked by other tools
as "suspicious".
(this is the same Thomas I interviewed recently about their
dataconflation strategies:
http://www.openstreetmap.org/user/joost%20schouppe/diary/40605
)

With Zors already checking all new mappers' changesets using the
welcome tool (thank you!), it might be interesting to see if we
can expand on that here too.

Here's some practical stuff from his e-mail:

> Is your process documented anywhere and is the code available?

  There is a "help" page, but it is in Lithuanian... Maybe google
translate can help:
http://patrulis.openmap.lt/pagalba.html


  Code (php+postgresql) is very basic and dirty (i'm not a web
developer) and I didn't have time to put it on github yet (planning to
do that for a year or so...). But code is also full of Lithuanian
comments and names...

  If somebody wants to have a look at it - I can share/send the code
and give any information required in English.

P.S. This patrolling stuff is integrated with QA tools (fetching a
list of errors from keepright, osmose as well as doing local error
checking) and data synchronisation tools. So "all in one" solution.
You get a list of unapproved changes, a list of not yet fixed errors
and a status of synchronisation of different items.

-- 
Joost Schouppe

OpenStreetMap
 | Twitter
 | LinkedIn
 | Meetup


___
Talk-be mailing list
Talk-be@openstreetmap.org 
https://lists.openstreetmap.org/listinfo/talk-be





___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be


___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] talk: "responding to vandalism"

2017-03-19 Thread Ben Abelshausen 
This is an excellent idea, perhaps we should discuss this the next hackday?
Or can someone try and set this up for Belgium?

Met vriendelijke groeten,
Best regards,

Ben Abelshausen

On Sun, Mar 19, 2017 at 6:07 PM, joost schouppe 
wrote:

> Hi,
>
> There is an interesting thread going on in the talk mailing list:
>
> https://lists.openstreetmap.org/pipermail/talk/2017-March/077672.html
>
> It started of with some complaining about vandalism, but it got
> interesting when Thomas Straupis started explaining how they work in
> Lithaunia. Basically, ALL changesets are validated. But changesets by
> "known mappers" are automatically approved, and some changesets are
> highlighted because they are marked by other tools as "suspicious".
> (this is the same Thomas I interviewed recently about their dataconflation
> strategies: http://www.openstreetmap.org/user/joost%20schouppe/diary/40605
> )
>
> With Zors already checking all new mappers' changesets using the welcome
> tool (thank you!), it might be interesting to see if we can expand on that
> here too.
>
> Here's some practical stuff from his e-mail:
>
> > Is your process documented anywhere and is the code available?
>
>   There is a "help" page, but it is in Lithuanian... Maybe google
> translate can help:
>   http://patrulis.openmap.lt/pagalba.html
>
>   Code (php+postgresql) is very basic and dirty (i'm not a web
> developer) and I didn't have time to put it on github yet (planning to
> do that for a year or so...). But code is also full of Lithuanian
> comments and names...
>
>   If somebody wants to have a look at it - I can share/send the code
> and give any information required in English.
>
> P.S. This patrolling stuff is integrated with QA tools (fetching a
> list of errors from keepright, osmose as well as doing local error
> checking) and data synchronisation tools. So "all in one" solution.
> You get a list of unapproved changes, a list of not yet fixed errors
> and a status of synchronisation of different items.
>
> --
> Joost Schouppe
> OpenStreetMap  |
> Twitter  | LinkedIn
>  | Meetup
> 
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

[OSM-talk-be] talk: "responding to vandalism"

2017-03-19 Thread joost schouppe 
Hi,

There is an interesting thread going on in the talk mailing list:

https://lists.openstreetmap.org/pipermail/talk/2017-March/077672.html

It started of with some complaining about vandalism, but it got interesting
when Thomas Straupis started explaining how they work in Lithaunia.
Basically, ALL changesets are validated. But changesets by "known mappers"
are automatically approved, and some changesets are highlighted because
they are marked by other tools as "suspicious".
(this is the same Thomas I interviewed recently about their dataconflation
strategies: http://www.openstreetmap.org/user/joost%20schouppe/diary/40605)

With Zors already checking all new mappers' changesets using the welcome
tool (thank you!), it might be interesting to see if we can expand on that
here too.

Here's some practical stuff from his e-mail:

> Is your process documented anywhere and is the code available?

  There is a "help" page, but it is in Lithuanian... Maybe google
translate can help:
  http://patrulis.openmap.lt/pagalba.html

  Code (php+postgresql) is very basic and dirty (i'm not a web
developer) and I didn't have time to put it on github yet (planning to
do that for a year or so...). But code is also full of Lithuanian
comments and names...

  If somebody wants to have a look at it - I can share/send the code
and give any information required in English.

P.S. This patrolling stuff is integrated with QA tools (fetching a
list of errors from keepright, osmose as well as doing local error
checking) and data synchronisation tools. So "all in one" solution.
You get a list of unapproved changes, a list of not yet fixed errors
and a status of synchronisation of different items.

-- 
Joost Schouppe
OpenStreetMap  |
Twitter  | LinkedIn
 | Meetup

___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be