> In any case all of the above potentially lead to your private fork of the
> planet getting out of sync real fast with the original, implying that
> applying diffs will become
> more problematic over time. So you wouldn't be able to take you fixed and
> known good planet fork, apply only
On 06/09/2018 01:56, Alan Brown wrote:
... I suspect the OSM community is not culturally disposed to that
form of moderation. So I will ask about a different approach.
One thing the OSM community _is_ culturally disposed to is people trying
things to see if they work, and in order to do there
OSM changesets or even the diffs only contain the changes to objects,
while in the simple case (somebody vandalising the name tag on NYC) that
may be enough to determine that something is "bad" for example messing
up a motorway exit will require you to actually apply (in one way or the
other) the
Hi,
Perhaps I didn't express it clearly, but my interest was in the idea that
certain. rather limited changelists could be flagged for moderation before they
are put into main dataset. There will always be things that seem like they
should be blocked, but are actually appropriate. In the
osmcha (osmcha.mapbox.com) already does most of this. While detecting
vandalism in general is difficult, edits like those in question are easy
to detect and small in number.
IMHO it really isn't an issue with openstreetmap in this case, as even
with the delay (somebody reported the user in
I tend to agree that automated systems are going to be not that useful.
I tend to notice some things in my area, but it's hard to keep track.
This makes me wonder about a tool that
- lets people sign up to watch edits, in some area, or in general,
sort of like maproulette. Use some
Hi,
On 05.09.2018 03:36, Alan Brown wrote:
> Granted, it would be nearly impossible to make this criteria perfect:
I think it would already be nearly impossible to make these criteria
even *good*. It is easy to come up with a knee-jerk "nobody should be
allowed to change the name tag of New
Other criteria for ranking a object for "change protection" could be
1) How long has it been since the last change to it.
2) How big is it. ( a long road would rank higher than a short one)
3) How many things are "attached to it"
4) How important is it. (Motorways are more important than
Alan,
Your phrase "The name tag of New York City should be an obvious example
- what would cause it to change" - That makes a lot of sense. To
further expand on this thought, identify and prioritize features in OSM
that theoretically should not change much at all over long periods of
time.
Hi -
I haven't commented on this forum for several years, but this event did catch
my attention.
There are some uses of OSM map data which would not allow for frequent updates
- offline uses - and therefore, a way of catching such vandalism immediately -
less than a day, even - would be very
On 8/31/18 5:58 AM, Rihards wrote:
>
> It gives us the same press as some vandals messing with wikipedia -
> let's not see it as a worse thing than it is.
>
> As a sidenote, this was detected and revert in OSM in a day. If data
> consumers would update the data more frequently, the impact would be
On 2018.08.30. 23:20, Kevin Kenny wrote:
> On Thu, Aug 30, 2018 at 10:39 AM Ian Dees wrote:
>>
>> Yes, the original harmful edit was made by user "MedwedianPresident" in
>> changeset https://www.openstreetmap.org/changeset/61555047 20 days ago. It
>> was then reverted by naoliv a day later:
>>
Hi,
On 30.08.2018 22:43, Frederik Ramm wrote:
> We can only speculate about the motives here
Ah, just a security researcher, I guess this makes it ok then?
https://reddit.com/r/openstreetmap/comments/9brqx4/this_is_medwedianpresident1_talking_what_i_did/
> frankly my money is on
> "attention
Hi,
On 08/30/2018 10:20 PM, Kevin Kenny wrote:
> A problem here is that it gives us a tremendous black eye in the
> press. I wonder how, moving forward, we can lessen the chances of
> this sort of hate speech propagating off the project.
We can only speculate about the motives here - frankly my
On Thu, Aug 30, 2018 at 10:39 AM Ian Dees wrote:
>
> Yes, the original harmful edit was made by user "MedwedianPresident" in
> changeset https://www.openstreetmap.org/changeset/61555047 20 days ago. It
> was then reverted by naoliv a day later:
>
On Thu, Aug 30, 2018 at 11:36 AM, Ian Dees wrote:
> Yes, the original harmful edit was made by user "MedwedianPresident" in
> changeset https://www.openstreetmap.org/changeset/61555047 20 days ago. It
> was then reverted by naoliv a day later:
> https://www.openstreetmap.org/changeset/61556585.
Yes, the original harmful edit was made by user "MedwedianPresident" in
changeset https://www.openstreetmap.org/changeset/61555047 20 days ago. It
was then reverted by naoliv a day later:
https://www.openstreetmap.org/changeset/61556585.
naoliv also blocked the user:
Never mind; I found it: https://www.openstreetmap.org/changeset/61555047
Looks like it was quickly reverted three weeks ago, but damn, it got
through to Mapbox anyway .
Thanks to whoever put the necessary safeguards in place to catch that
stuff, and to who reverted it.
-Bill
On Thu, Aug
Does anyone know if this is traceable to OSM, or was it limited to Mapbox's
mirror? I can't seem to find a related changeset, in any case . . .
https://www.bbc.com/news/technology-45354311
-Bill
___
Talk-us mailing list
Talk-us@openstreetmap.org
19 matches
Mail list logo
