Siteadmin, Check users, nsTeam1RO, nsTeam1RW, nsTeam1_talkRO, nsTeam1_talkRW, oversight, Administrators
30,650
edits
Changes
Jump to navigation
Jump to search
Line 54:
Line 54: + +
Conservapedia:Desk/Abuse (view source)
Revision as of 17:23, December 4, 2008
, 17:23, December 4, 2008→Range Blocks: Not a public matter
::In the future, I think that the range blocks should be performed by you, Geo (an actual administrator). The thought that I actually had to run checkuser over the IP's blocked and finding a seemingly legitimate contributor worries me. Block ranges need to be sharply defined. The larger the range, the shorter the block. I'd prefer to see a /24 range (256 IP's) for infinite duration rather than a /16 range for 1 year. I don't think we will worry Andy with the ipblock-exempt right as the problem can be prevented by using better range blocking methods. [[User:Jallen|Jallen]] 22:46, 3 December 2008 (EST)
::In the future, I think that the range blocks should be performed by you, Geo (an actual administrator). The thought that I actually had to run checkuser over the IP's blocked and finding a seemingly legitimate contributor worries me. Block ranges need to be sharply defined. The larger the range, the shorter the block. I'd prefer to see a /24 range (256 IP's) for infinite duration rather than a /16 range for 1 year. I don't think we will worry Andy with the ipblock-exempt right as the problem can be prevented by using better range blocking methods. [[User:Jallen|Jallen]] 22:46, 3 December 2008 (EST)
It's better not to discuss range blocks. If '''you''' can't access CP because of a range block, contact a sysop via email. --[[User:Ed Poor|Ed Poor]] <sup>[[User talk:Ed Poor|Talk]]</sup> 12:23, 4 December 2008 (EST)
==Interference and Collusiveness==
==Interference and Collusiveness==