Changeset list getting clobbered by MapRoulette...

[Martijn van Exel]

I'm curious - what are actual changes? The MapRoulette changesets
contain 'actual changes' as far as I am concerned, so how would that
filter help this situation?

On Thu, Nov 8, 2012 at 8:45 AM, Paweł Paprota <ppawel at fastmail.fm> wrote:
> On 11/08/2012 04:36 PM, Serge Wroclawski wrote:
>>
>> On Thu, Nov 8, 2012 at 2:45 AM, Richard Fairhurst <richard at systemed.net>
>> wrote:
>>>
>>> On 08/11/2012 02:02, Jeff Meyer wrote:
>>
>>
>>> It's a known issue but far from trivial to fix.
>>
>>
>> For PL2, there could be an additional argument on the address bar that
>> is some freeform field for the changeset to have in its tags,
>> something that indicates its from a remote request, etc.
>>
>> For Josm, this could be done too.
>>
>> Then, someone could set up a filter and filter based on changeset tags.
>>
>> Just as (in theory) one could filter out the bots, if the bots were
>> well behaved.
>>
>
> This would get rid of those changesets completely so it's not a good
> solution.
>
> The correct solution is to show the automated/large changesets where they
> make actual changes and don't show them where they don't.
>
> Paweł
>
>
>
> _______________________________________________
> rails-dev mailing list
> rails-dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/rails-dev



-- 
martijn van exel
http://oegeo.wordpress.com