QUOTE(SirFozzie @ Sat 5th January 2008, 5:30pm)
![*](style_images/brack/post_snapback.gif)
Actually, it's really a catch-22, If we DON'T mention who it is in the block log, and say "Sockpuppet" or "Checkuser-proven sockpuppet" not only is there no transparancy in the process, but we get clobbered with accusations that it's not reaaaaaaaaaaaaaaallly a sockpuppet or proven by checkuser, but just blocking folks we don't like.
And the real name thing is a subset. If someone is proven to be a sockpuppet of the account Joe Schmoe (Joe's real name was used for an account).. can we get by just by saying "Sockpuppet of a Real-Life name account?" or would we get called on that as well?
QUOTE(Lar @ Sat 5th January 2008, 6:06pm)
![*](style_images/brack/post_snapback.gif)
AB, what do you suggest be done in future, in view of what SirFozzie points out?
It's only a problem because the WP community and checkusers
are so prideful that they cannot accept that they are not infallible,
that innocent people get blocked sometimes, and for that matter,
that there may be good reasons (ethically) for sockpuppetry.
I can guarantee you they are not infallible. There are no foolproof
methods of identifying sockpuppets. IP addresses do not
correspond 1:1 to human beings,* writing analysis is even more
fuzzy, and they aren't experts at it. At best, its probabilistic, but
their pride blinds them from being aware of that. One would think
confessions, at least, would be reliable, but when a confession can
be the only way to get unblocked, are they really so reliable?
Innocent or guilty, its still a privacy violation. The consequences of
outing can be severe, and a semblance of an encyclopaedia isn't
enough to justify that. Preventing certain types of sockpuppetry is
a WP rule, not a higher ethical principle. And, if innocent, that's salt
in the wound, since it is also defamation.
The solution, then, is to drop all pretence of justice. No privacy
violations, no defamation, just block because 'it's our site and we
feel like blocking you'. And don't make the block logs public - it's
no one's business, too many people think WP has good judgement,
when in fact it's judgement is so bad it doesn't even know it has
bad judgement, so it is necessary to hide the block log to protect
the reputations of the blockees. Hell, most sites do not publish
their block logs - they just block people at whim. It works fine.
WP needs to stop pretending to be the High Court of the Internet
and just admit they block people on whims. That would be honest.
* Checkuser yields imperfect results. IP addresses simply do not correlate 1:1
to human beings, or even computers. Reasons for this include:
- Dynamic Host Configuration Protocol - IPv4 addresses are limited in quantity,
and IPv6 is not catching on. So, rather than needing an IP address for each
separate client (where a client may be a computer or a NAT, as explained later),
an Internet Service Provider (ISP) only needs enough IP addresses for the number
of clients that are online at one time. The automated nature of Dynamic Host
Configuration Protocol (DHCP) also makes it convenient. Note that there are
different degrees of dynamicness - an IP address is assigned for a limited but
adjustable period of time, and a DHCP server may or may not try to give a client
the same IP address as it had before (note that there are ways of getting the DHCP
server to give you a new IP address). Dial-up tends to be highly dynamic. - Overloading or overlapping network address translation (NAT) - This is another
solution to the IPv4 address scarcity problem. Basically, multiple clients share the
same IP address, with a router converting packets sent to that IP address to packets
sent to various local IP addresses, and vice versa. This can be done at multiple
levels - a household, a school, library, or business, or even an entire ISP. - Shared computers - internet cafes, libraries, families. Note that a group of computers,
at an internet cafe for example, are quite likely all behind the same NAT anyway. - Things change. People switch ISPs.
- Do anonymising proxies - both closed and open - even need to be listed?
Chances are, you are either behind a NAT of some size, have a dynamic IP address,
or, quite likely, both.