Wikipedia talk:IP block exemption/log
From Wikipedia, the free encyclopedia
Please just leave a short message here as to what you did, what happened, what you think could be done better, and sign it, so we have a date. Thanks! :-) Of course, what we really want you to do is also boldly edit the policy page, so that others can learn from your experience, but if you're not quite feeling up to that, we can live with just leaving a statement here.
* Watch out for confirmation bias here of course. Despite that, comments are quite useful for making improvements. Just don't expect statistical accuracy
- Exempted Ride the Hurricane (talk · contribs · deleted contribs · logs · block user · block log) (email request). Checkuser confirms user is affected by a hard-blocked IP range used by a "temporary account" vandal. Users contribs are few but no sign of vandalism, no block log, edits go back a year. Somewhat apprehensive in case we get sleepers requesting exemption, but if we do we can deal with them - if they use anonymity we remove the exemption anyway. Still curious how this request came to me, less than 24 hours after the right was enabled, by a user who only rarely edits. Time will tell if the exemption is reasonable. FT2 (Talk | email) 17:02, 9 May 2008 (UTC)
- Exempted 718 Bot (talk · contribs · deleted contribs · logs · block user · block log) (IRC request). Bot operates from a large hardblocked range. Currently a hard to manage system of layered blocks was used to permit editing. [1] This flag will permit full blocking of the disruptive range. [2] As this full block negates the risk of east718 running unknown abusive accounts, there is an acceptably low risk of violative behavior. MBisanz talk 01:57, 10 May 2008 (UTC)
- Exempted Oolon Colluphid (talk · contribs · deleted contribs · logs · block user · block log) (request by {{unblock}} template). User edits from a recently hard-blocked range and from another with pretty much every IP on long-term block (confirmed by CU). Not a great breadth of contributions, but there is no reason to think abuse is likely. This exemption should, barring abuse, stay in place until this rangeblock expires. Sam Korn (smoddy) 21:13, 10 May 2008 (UTC)
- Exempted Man with a tan (talk · contribs · deleted contribs · logs · block user · block log). The original request was by an anonymous user by use of {{unblock}} who was covered by this rangeblock. I had him email me his desired account name and created the account, then had him confirm that he had taken possession of the account, also checking that he used an IP address from that range. As it is an account without any editing history, I shall be particularly checking to ensure that he does not use the account for anonymising proxies. Sam Korn (smoddy) 10:58, 11 May 2008 (UTC)
- Lighthead (talk · contribs · deleted contribs · logs · block user · block log), edits from the range most commonly used by Grawp, in order to hardblock the range. I did this as checkuser before applying the rangeblock, without being asked by the user. Thatcher 14:37, 14 May 2008 (UTC)
- Tholly (talk · contribs · deleted contribs · logs · block user · block log) User was making useful contributions (and was being affected by a hard rangeblock, and after consulting with a checkuser on IRC, I granted an exemption. SQLQuery me! 17:00, 15 May 2008 (UTC)
- Several more. (bots this time)
- ClueBot (talk · contribs · deleted contribs · logs · block user · block log)
- ClueBot II (talk · contribs · deleted contribs · logs · block user · block log)
- ClueBot III (talk · contribs · deleted contribs · logs · block user · block log)
- ClueBot IV (talk · contribs · deleted contribs · logs · block user · block log)
- Reasons:
- Most of these bots are critical (At least Cluebot is), they run from shared hosting (which, in most cases can get frequently rangeblocked as soon as one idiot runs a php proxy)
- So that blocks on the individual bots can be made in case of malfunction without affecting the more critical ones (in case 'autoblock disabled is forgotten')
- And, because they will be moving to a school network soon, which will be MUCH more prone to rangeblocking. SQLQuery me! 20:53, 15 May 2008 (UTC)
- Reasons:
Dihydrogen Monoxide (talk · contribs · deleted contribs · logs · block user · block log) Affected by filtering software at school and forced to use TOR. east.718 at 08:40, May 23, 2008- Now redundant. --Kim Bruning (talk) 10:30, 29 May 2008 (UTC)
- Exempted Kick52 (talk · contribs · deleted contribs · logs · block user · block log), affected by this block. -- lucasbfr talk 14:39, 25 May 2008 (UTC)
- Dihydrogen Monoxide (talk · contribs · deleted contribs · logs · block user · block log) User applied to unblock-en-l for IP block exemption. Consensus was (unanimously) reached to grant the right. Sarah 09:19, 28 May 2008 (UTC)