Fixing subway stations in Rome wouldn't be prohibited to newcomers if
they limit themselves for that day to Rome, encouraging them to focus
on an area rather than jumping around the globe changing things (True
value of OSM is _local_ knowledge!). They could be first only allowed
to map
--- On Sun, 12/7/09, MP singular...@gmail.com wrote:
(long road routes across US/australia or even flights - one
user in
Even the current limits make it time consuming downloading multiple areas to
cover drives in rural areas I've taken in the last month alone.
Hi!
First, some clarifications:
The possible measures and use limitations were only provided as an
example what can be observed and measured and what could be limited
before earning enough trust in a wat that would be much more effective
and less annoying than captchas. It was not a specific
What about not adding restrictions to the rights, but implement some
warning system?
We can use some trust points that are awarded for good mapping
(objects that last on the map)
Then warning points in each upload for possibly bad things (deleted
nodes, removed tags, accidentally moving many
--- On Sat, 11/7/09, Stefan Baebler stefan.baeb...@gmail.com wrote:
Fixing subway stations in Rome wouldn't be prohibited to
newcomers if
they limit themselves for that day to Rome, encouraging
them to focus
on an area rather than jumping around the globe changing
things (True
Hopefully
Hello,
Goal
Prevent creation of new sock puppet accounts for potential acts of
vandalism on larger scale and spam. Gradually give trust to users, and
give them additional privileges. It should not be in the way when new
users want to contribute normally. It should not encourage competition
As osm grows the chances that somone will try to damage the map grows.
Maybe a new user should have their edits checked when they first join and
then build trust that way. Make it a random check but put the priority on
the new users. If somone does a large edit then it can be flagged to be
Agreed,
Trust points not needed.
The system in place now, which prevents vandalism, is of users all the time
always have their eyes on the map.
Unlike other websites, which bots might manage. .. we have actual people
always watching it.
The instant that new edits are made, everyone is aware of
--- On Fri, 10/7/09, Jack Stringer jack.ix...@googlemail.com wrote:
As osm grows the chances that somone
will try to damage the map grows.
Maybe a new user should have their edits checked when
they first join and then build trust that way. Make it a
random check but put the priority on the
On Fri, Jul 10, 2009 at 12:01 PM, Sam Vekemans acrosscanadatra...@gmail.com
wrote:
Ie. in Montreal someone accidentally moved a bunch of stuff (a newbie) it
was reported on the talk-ca list, they messaged that user so to see if it
was a bot or a person. And it was a person, who made an
I don't realistically see an automated reputation system working given the
community we have but how about a mentoring type approach where experienced
mappers adopt one or more newbies.
When someone signs-up for the project (or maybe when they make their first
edit) they could be given a list of
--- On Fri, 10/7/09, Kevin Peat ke...@kevinpeat.com wrote:
I don't realistically see an
automated reputation system working given the community we
have but how about a mentoring type approach where
experienced mappers adopt one or more newbies.
Well it would have saved a lot of newbie
2009/7/10 Peter Dörrie peter.doer...@googlemail.com
Well, as the OSM community grows exponentially at the moment we will run
out of expereinced mappers pretty soon ...
There might be exponential growth in accounts opened by lurkers, bots, and
spammers but I don't think the growth in people
When someone signs-up for the project (or maybe when they make their first
edit) they could be given a list of available mentors preferably in their
local area but failing that you
Cool, perhaps there could be a way that on the list of the 10 local mappers
in the area, to sort those who have
this, but the way
the editors handle the tiger:reviewed=no tag would probably be a good
framework to build off of.
Chris Hunter
chunter...@gmail.com
From: Kevin Peat ke...@kevinpeat.com
To: John Smith delta_foxt...@yahoo.com
Date: Fri, 10 Jul 2009 13:00:26 +0100
Subject: Re: [OSM-talk] OSM
15 matches
Mail list logo