Please remember to:
Some users seems to not be able to think through the consequences of blocking whole ranges, and block telecom providers in their own country. I'm not quite sure how this should be handled, but when someone with access to IP-blocks hear that they can do a IP-block and be rid of a minor problem they think this is safe. Please DO NOT tell them to do so. A range block like /16 can easily escalate to several thousand users if they are NAT'ed. I even have examples on users blocking more than a million addresses and claiming that it is safe because some CU-user said so. Of course you don't. — Jeblad 19:16, 2 October 2016 (UTC)
- As someone who's been doing this a lot I can say that my solution was to forward the affected users (via the block reason) to a page like this one, so they at least know what's wrong and what can be done about it. That being said, I mostly block that way networks, which are unlikely to host local users: not national and—at least as much as it can be guessed from whois and other similar info—not end-user networks, but rather collocation, hosting, etc. For the national networks and those that seem end-user related, the blocks are much shorter in duration and relaxed in their restrictions, but there is still an appropriate page with explanation and instructions. While this solution is far from ideal, it seems to work reasonably well for our project, cutting significantly on the open proxy vandalism and harassment with few complaints so far. But it likely wouldn't work that well on more active projects, where also many users are expected to edit from abroad, and it'll certainly not work at all on e.g. the English Wikipedia or Commons.
— Luchesar • T/C 06:28, 7 October 2016 (UTC)
- The CheckUser extension can't block you. There is always some user behind of it, and blocks are not doing without a good reason. --Stryn (talk) 19:33, 13 January 2017 (UTC)
Limited Checkuser for all users?
I think it would help prevent sockpuppets a lot more if all users had a limited check-user-like ability. Now, clearly not all users should have access to the actual content of the check user information (they shouldn't have access to the underlying technical data including client IP address, HTTP user agent, cookies, etc.). Instead, what if all users had the ability to see if any two accounts had ever shared the same client IP address? All you would get are "plausible" (they shared the same IP at least once), or "impossible" (they never shared the same IP). It wouldn't prove that the two accounts are actually the same person (more detailed look at the technical data by an actual check user would be needed for that along with their behavior), but it would be enough to at least examine it closer. Also it couldn't be used when one of the accounts is an IP account (as that would reveal the underlying technical data about the non-IP user). Can anyone identify any potential privacy problems with this? -Obsidi (talk) 18:31, 5 May 2017 (UTC)
maybe 75 days. not 90