Changes

Jump to navigation Jump to search
m
Deletion
Line 27: Line 27:  
#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.
 +
 +
==Deletion==
 +
Sysops should be careful not to delete other sysops talk page comments, including on their user pages.
    
==Moving==
 
==Moving==
Block, Siteadmin, SkipCaptcha, Upload, Automoderated users, delete, edit, move, nsTeam2RO, nsTeam2RW, nsTeam2_talkRO, nsTeam2_talkRW, protect, rollback, Administrators, template
293,079

edits

Navigation menu