I haven't read the whole thread, so apologies if I'm repeating something.
How about we introduce into editors (that advanced users use) a default
behaviour that at above a certain zoom level, all features that have been
edited in the last 24 hours are somehow colourised. Features edited between
1
On 20.03.2017 18:23, Mikel Maron wrote:
For example (this may have been mentioned before on the thread) .. the
OSM US community has set up a Slack channel with notifications of every
new user editing. We monitor this channel, give a quick look at edits,
and send welcome emails. That said, it's an
Here are two accounts which have spam (SEO) user description page and
have vandalized the map:
http://www.openstreetmap.org/user/Morland
http://www.openstreetmap.org/user/Mlafagos
Just for a reference for another vandal motivation (doubly stupid,
first - rel=nofollow being used on osm.org and secon
Just to add one more comment to what has been a very useful thread
discussing the options available:
At no time did anyone see fit to actually try and get in touch with the
user who made these edits explaining what OSM is and trying to win them
over from "mapping for Pokemon" to mapping things
Hi
Frederik wrote
> Hence, the #1 strategy against "there's no local community that helps newbies
>and reports vandals" for me is always: Attract a local community. Put more
>cynically: A map without a local community is not able to survive, and has
>never been, and it was perhaps a mistake to
Since it was first announced in october 2015, I have been watching the demo
instance of https://github.com/MichaelVL/osm-analytic-tracker (developed by a
fellow dane) almost daily and have found it immensely useful for keeping track
of the activity in all of Denmark (the country north of Germany
On 17.03.17 20:22, Jakob Mühldorfer wrote:
Google tried to have restrictions on new editors
The map got vandalised anyways and they shut down public editing
So basically what others said, not in favour of any kind of restrictions.
I also think it is impossible to stop vandalism by a single tech
>
>
> Now here what has to be done is an appropriate testing mechanism.
> There are some functionality already done (like the one in Belgium),
> but the problem is that everybody sees ALL last changes, there is no
> way to SHARE the work of checking and you never know if somebody has
> already chec
On Fri, Mar 17, 2017 at 2:02 PM, Yves wrote:
> Interesting, I didn't know such patrolling took place at a country scale
> in OSM. Have you revert/re-map stats?
>
> However with your point 1)you have an idea.
> How about a service rendering the area affected by an edit before 'commit'?
> This prev
On Thu, Mar 16, 2017 at 2:27 PM, Nicolás Alvarez
wrote:
> 2017-03-16 16:00 GMT-03:00 Mike N :
> > On 3/16/2017 2:04 PM, Frederik Ramm wrote:
> >>
> >> And in vandalism, I would also distinguish between teenage doodles
> >> ("penis! ha ha ha!"), and serious concerted efforts to harm OSM.
> >
> >
>
On Thu, Mar 16, 2017 at 1:00 PM, Michael Reichert wrote:
> I can second that. I did Pokémon cleaning in Germany. The majority of
> them doesn't edit OSM a second time.
>
In defense of PoGo for a moment...
I've actually been fairly impressed with this in my region. We've had a
few new casual ma
On Thu, Mar 16, 2017 at 12:44 PM, Dave F
wrote:
>
> On 16/03/2017 17:13, James wrote:
>
>> People can't even be bothered to review osmcha, you think people will
>> want to approve changesets?
>>
>>
> Could that be because it's not the very user friendly site? The filter
> options are overly compl
> 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
On Fri, Mar 17, 2017 at 8:50 AM, Tomas Straupis
wrote:
>
> What we are doing in Lithuania for the last 5 years or so is we have a
> patrolling mechanism similar to wikipedia. That is all changesets in
> the region (in our case in Lithuania) are filtered out and placed into
> "check list". If the
> Interesting, I didn't know such patrolling took place at a country scale in
> OSM. Have you revert/re-map stats?
No, such stats are not collected. And it would be hard to do that,
because it is not yes/no. Sometimes it's just a minor problem,
sometimes it is something much worse. Until appeara
Google tried to have restrictions on new editors
The map got vandalised anyways and they shut down public editing
So basically what others said, not in favour of any kind of restrictions.
Am 16.03.2017 um 14:47 schrieb Manohar Erikipati:
Hi all,
Last saturday, Central park in New York City was
Interesting, I didn't know such patrolling took place at a country scale in
OSM. Have you revert/re-map stats?
However with your point 1)you have an idea.
How about a service rendering the area affected by an edit before 'commit'?
This preview could be the place for an additional warning about
Let's get on the higher level first.
There are two ways of doing it from the process perspective:
1) EDIT->TEST->COMMIT
2) EDIT->COMMIT->TEST
The first one gives higher quality but also discourages edits and
maybe even prohibits edits in areas with no/few "checkers".
So obviously the way to go f
On Fri, Mar 17, 2017 at 7:03 AM, Rory McCann wrote:
> But the advantage is that we get a free, global map. IMO new users being
> able to see their changes on the map is very powerful, and makes them
> more likely to continue to edit. I don't think we would have the map we
> have today if people n
It's a shame that this happened, ideally it shouldn't and it should be
be fixed faster. But I don't think we should give up the "wiki" aspect.
Everyone, even new users, should be able to edit the "live" database.
Which yes, will have disadvantages.
But the advantage is that we get a free, glob
2017-03-16 20:00 GMT+01:00 Mike N :
> Then there's the serious and real ha ha ha
> http://www.openstreetmap.org/#map=19/41.84196/-89.48580
>
> http://chicago.cbslocal.com/2013/10/31/from-the-sky-dixon-ch
> urch-looks-like-a-penis/
>
likely intentional, the "view from the sky" is the same as th
2017-03-16 16:01 GMT+01:00 James :
> 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)
+1, recently there was a proof of concept of
2017-03-16 16:00 GMT-03:00 Mike N :
> On 3/16/2017 2:04 PM, Frederik Ramm wrote:
>>
>> And in vandalism, I would also distinguish between teenage doodles
>> ("penis! ha ha ha!"), and serious concerted efforts to harm OSM.
>
>
> Then there's the serious and real ha ha ha
> http://www.openstreetmap
On 3/16/2017 2:04 PM, Frederik Ramm wrote:
And in vandalism, I would also distinguish between teenage doodles
("penis! ha ha ha!"), and serious concerted efforts to harm OSM.
Then there's the serious and real ha ha ha
http://www.openstreetmap.org/#map=19/41.84196/-89.48580
http://chicago.c
Hi,
I find it a bit unfortunate that you have chosen to use "vandalism"
in the subject, even though you later write
On 16.03.2017 14:47, Manohar Erikipati wrote:
> ... protect the map against common mistakes and intentional attacks.
I think that "common mistakes" (mostly, beginner's mistakes
Hi Manohar,
Am 2017-03-16 um 14:47 schrieb Manohar Erikipati:
> - 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,
Hi,
Am 2017-03-16 um 15:48 schrieb Clifford Snow:
> 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
> pokem
Hi,
On 16.03.2017 15:46, Bas Couwenberg wrote:
> OSM lacks a good staging area where new contributors can experiment and
> learn without breaking the production data.
I had offered the technical infrastructure for this
https://lists.openstreetmap.org/pipermail/dev/2016-November/029557.html
but
On 16/03/2017 17:13, James wrote:
People can't even be bothered to review osmcha, you think people will
want to approve changesets?
Could that be because it's not the very user friendly site? The filter
options are overly complicated & doesn't even save them!
DaveF
---
This email has bee
On 03/16/2017 06:13 PM, James wrote:
> People can't even be bothered to review osmcha, you think people will want
> to approve changesets?
Eventually, yes. It will become part of a responsible and thriving local
community. Debian managed to transition from a free-for-all (just
mailing the project
Another approach is a middle player between the raw DB and the data consumers.
Yves ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
People can't even be bothered to review osmcha, you think people will want
to approve changesets?
On Mar 16, 2017 1:07 PM, "Sebastiaan Couwenberg" wrote:
> On 03/16/2017 05:30 PM, James wrote:
> > and maintainers privileges, would be determined by whom? Other
> maintainers?
>
> Yes, the local co
On 03/16/2017 05:30 PM, James wrote:
> and maintainers privileges, would be determined by whom? Other maintainers?
Yes, the local community grants that privilege.
When the local community is dysfunctional there is the overriding
authority of OSMF WGs like DWG. Like we have the Technical Commitee
and maintainers privileges, would be determined by whom? Other maintainers?
Then you have whats going on on Wikipedia Fr where it's controlled by a
small group of close friends that refuse anything outside their norms,
which is bad.
On Thu, Mar 16, 2017 at 12:17 PM, Bas Couwenberg wrote:
> On 20
On 2017-03-16 16:01, James wrote:
Even if we had a Git pull request sort of mechanism, who would
"approve"
edits?
Anyone with maintainer priviledges in the respective local community.
This privilege is earned by proving skill.
Kind Regards,
Bas
2017-03-16 16:15 GMT+01:00 Clifford Snow :
>
> On Thu, Mar 16, 2017 at 8:03 AM, Jean-Marc Liotier wrote:
>
>> Users who have invested into a number of Openstreetmap contributions
>> seldom spend their karma into vandalism, so my experience is that
>> patrolling contributions by new users catches
On Thu, Mar 16, 2017 at 8:03 AM, Jean-Marc Liotier wrote:
> Users who have invested into a number of Openstreetmap contributions
> seldom spend their karma into vandalism, so my experience is that
> patrolling contributions by new users catches most deliberate mayhem.
>
+1
--
@osm_seattle
osm
On Thu, 16 Mar 2017 07:48:10 -0700
Clifford Snow wrote:
>
> a bot running on slack and IRC 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
Use the excellent
http://resultmaps.neis-one.org/newestosmcreatefeed.
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. Put
On Thu, Mar 16, 2017 at 6:47 AM, Manohar Erikipati
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
On 2017-03-16 14:47, Manohar Erikipati wrote:
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
Hi all,
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
https://www.openstreetmap.org/changeset/46756622
- 46756461 renamed Central park in
https://www.openstreetmap.org
42 matches
Mail list logo
