Changes

Jump to navigation Jump to search
m
Line 31: Line 31:  
#If you have determined a user should be blocked, there are multiple more factors to consider:
 
#If you have determined a user should be blocked, there are multiple more factors to consider:
 
##Should the user be blocked for a reason not based on the quality of his edits or legitimacy? (For example, a vulgar username.) Then make sure the checkbox titled: "'''Automatically block the last IP address used by this user...'''" is unchecked (it is checked by default) so that the user can create a new account.
 
##Should the user be blocked for a reason not based on the quality of his edits or legitimacy? (For example, a vulgar username.) Then make sure the checkbox titled: "'''Automatically block the last IP address used by this user...'''" is unchecked (it is checked by default) so that the user can create a new account.
−
##If the user should be blocked based on his actions on the wiki, carefully consider how long  the user should be blocked. If the user is a blatant vandal, generally 6 month blocks are handed out. If the user is merely edit warring or some similar offense, perhaps a shorter block (2 days, a few weeks, months?) might be more appropriate. Keep in mind that users and IP addresses can change - long term and infinite blocks are therefore discouraged.
+
##If the user should be blocked based on his actions on the wiki, carefully consider how long  the user should be blocked. If the user is a blatant vandal, generally 6 month blocks are handed out. If the user is merely edit warring or some similar offense, a shorter block (2 days, a few weeks, months?) is more appropriate after warnings are given out. Keep in mind that users and IP addresses can change - long term and infinite blocks are therefore discouraged.
 
#If you have run checkuser (which you should generally only do with probable cause) and determined the user has created sock-puppet accounts, the user should be blocked. Be wary that multiple distinct users might just be editing from a public location - for example a school, a coffee house or a library.
 
#If you have run checkuser (which you should generally only do with probable cause) and determined the user has created sock-puppet accounts, the user should be blocked. Be wary that multiple distinct users might just be editing from a public location - for example a school, a coffee house or a library.
 
#Furthermore, users with blocking rights must be very careful in the issuance of a block. Unwarranted blocks that may be undone clog the block log, and future Administrators may unfairly consider an established user as a troublemaker, when the real problem lies with an unjustifiable block made by an Administrator. When a blocking error occurs, it's best for everyone involved for the original blocking editor to undo the action so as to limit confusion. However, this is not always possible.
 
#Furthermore, users with blocking rights must be very careful in the issuance of a block. Unwarranted blocks that may be undone clog the block log, and future Administrators may unfairly consider an established user as a troublemaker, when the real problem lies with an unjustifiable block made by an Administrator. When a blocking error occurs, it's best for everyone involved for the original blocking editor to undo the action so as to limit confusion. However, this is not always possible.
Block, Siteadmin, SkipCaptcha, Upload, Automoderated users, delete, edit, move, nsTeam2RO, nsTeam2RW, nsTeam2_talkRO, nsTeam2_talkRW, protect, rollback, Administrators, template
292,964

edits

Navigation menu