On Nov 18, 2016 05:09, "Gergo Tisza" wrote:
>
> On Sat, Nov 12, 2016 at 12:02 PM, Brion Vibber
> wrote:
>
> > 1) Eliminate IP address exposure for non-logged-in editors. Those
editors
> > should be either given a random, truly anonymous identifier, or
On Thu, Nov 17, 2016 at 11:09 PM, Gergo Tisza wrote:
>
> the ability to claim recent anonymous edits when you register.
>
Here, here. I'm sure my IP address is lying around in lots of places in
the wikidump because I forgot to log in or my cookie expired and I never
On Sat, Nov 12, 2016 at 12:02 PM, Brion Vibber
wrote:
> 1) Eliminate IP address exposure for non-logged-in editors. Those editors
> should be either given a random, truly anonymous identifier, or required to
> create a pseudonym as a login.
>
I filed
In addition, we'd be making significantly more difficult the detection and
mitigation of abusive anonymous editing. Currently, when someone edits as
an IP, gets blocked, resets their router, and changes the last octet, we
can easily tell they're socking around a block. And to mitigate that, we
can
Honestly I cannot find pros since it's a free choice to edit without
logging, so it's not up to me to find them :D if it would depend solely on
me this thread would even exist ;)
Meanwhile I weight in the biggest con: the inability to use rangeblocks and
an unacceptable weakening of our ability
While it is tempting to start with cons, I think for most of the community
members, the question will be: 'what alternatives are there to accomplish
more or less the same' with regards to fighting vandalism and sockpuppetry.
And answering that question would start with describing how we actually
A fully enumerated list of "cons" would be an important place to start.
Wikimedians and WMF have long promoted the existence of stuff ike the
"Congress edits" twitter account, which reports account-less edits from
capitol hill. We often block high school IP addresses at certain times in
the
The biggest privacy problem in Wikipedia has always been the permanent
public exposure of casual editors' IP addresses.
Secondarily, we store logged-in editors' IP addresses for a limited time,
exposing all editors' IP addresses to access by staff and volunteer
accounts which could be stolen or