| Line 1: |
Line 1: |
| | + | {{Delete}} |
| | <span style="color:darkblue">'''If you are reading this for the first time, congratulations! You have joined a group of editors here to protect Conservapedia, and act as "stewards" of the project. Below are some guides that will make you more effective and a better example to editors in your job as a Sysop:''' </span> | | <span style="color:darkblue">'''If you are reading this for the first time, congratulations! You have joined a group of editors here to protect Conservapedia, and act as "stewards" of the project. Below are some guides that will make you more effective and a better example to editors in your job as a Sysop:''' </span> |
| | {| style="float:right; background:#DEF; border:solid 1px darkblue; padding:5px;width:300px" | | {| style="float:right; background:#DEF; border:solid 1px darkblue; padding:5px;width:300px" |
| Line 19: |
Line 20: |
| | | | |
| | Incivility and personal attacks should be replaced with the {{[[Template:personal remark removed|personal remark removed]]}} template. As a last resort, and in the most extreme circumstances, the sysop or blocking editor may have to resort to a block. | | Incivility and personal attacks should be replaced with the {{[[Template:personal remark removed|personal remark removed]]}} template. As a last resort, and in the most extreme circumstances, the sysop or blocking editor may have to resort to a block. |
| | + | |
| | + | The {{[[Template:Hide collapse|hide collapse]]}} template could be used when a posting derails, either purposely or unwittingly, the original topic thread. However, the template needs to be used with caution and not simply as a means to silence critics. Ideally, the original creator of the topic thread would use the template if they feel a poster is attempting to derail the topic with excess, superfluous information, or off-topic derailment. |
| | | | |
| | ==Vandalism== | | ==Vandalism== |
| − | In dealing with vandalism, Page Protect after Reversion should be the first method. It is important to create a Log of attacks. Duration of the Protect should be at last 1 Hour, and possibly as long as 6 months after a repeated pattern of attacks on that particular article Mainspace has been established. Some High traffic pages need longer protection, but those are rare exceptions. Blocking a new user should not be the first immediate, impulsive response, unless profanity or other serious violations occur. Some newbies need time to learn the rules, guidance, encouragement, and interaction from other users to become good productive editors. | + | In dealing with vandalism, Page Protect after Reversion should be the first method. It is important to create a Log of attacks for other Admin to see. Duration of the Protect should be at least 1 Hour, and possibly as long as 6 Months after a repeated pattern of attacks on a particular article Mainspace has been established. Some High traffic pages need longer protection, but those are rare exceptions. Blocking a new user should not be the first immediate, impulsive reaction, unless profanity or other serious violations occur. Some newbies need time to learn the rules, guidance, encouragement, and interaction from other users to become good productive editors. |
| | + | |
| | + | The vandals are showing you their interests, or what is stuck in their craw, so take advantage of their lapse in judgement to force them to ask permission to make changes. Experience shows that immediately resorting to Blocking does not, and cannot, stop a determined vandal. Use their weakness and revelations of personal bias to lead you to what Mainspaces need Page Protect, and frustrate their ambitions. Immediate resort to Blocking only serves to multiply, exponentially, the use of sockpuppets by enemies of the site. |
| | | | |
| − | The vandals are showing you their interests, or what is stuck in their craw, so take advantage of their lapse in judgement to force them to ask permission to make changes. Experience shows that immediate resorting to Blocking does not, and cannot, stop a determined vandal. Use their weakness to lead you to what Mainspaces need Page Protect. Immediate resort to Blocking only serves to multiply, exponentially, the use of sockpuppets by enemies of the site.
| + | Remember, Vandal patrol is not simply a game of whack-a-mole or Space Invaders where you get to zap your opponents. It entails defending the wiki while not doing harm to growing our userbase. |
| | | | |
| | ==Blocking== | | ==Blocking== |
| Line 29: |
Line 34: |
| | #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 2 or 5 year 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 - 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. Use the Edit summary to create a permanent record for blocking justification. |
| | + | #The primary purpose of the blocking tool is aimed at behavior modification, not [[vengeance]]. |
| | | | |
| | === Guideline concerning avoiding unwarranted blocks === | | === Guideline concerning avoiding unwarranted blocks === |
| Line 37: |
Line 43: |
| | Editor retention is important for [[wiki]]s. Therefore, unwarranted blocks are to be avoided and the benefit of the doubt should be given to editors so editors are not blocked due to good faith mistakes and/or mistakes due to ignorance of wiki policies. | | Editor retention is important for [[wiki]]s. Therefore, unwarranted blocks are to be avoided and the benefit of the doubt should be given to editors so editors are not blocked due to good faith mistakes and/or mistakes due to ignorance of wiki policies. |
| | | | |
| − | For example, many new wiki editors are not aware that they cannot copy and paste a material from other wikis or other websites without giving attribution (quoting material). If a new editor were to do such a thing, he should be cordially warned and not blocked. | + | For example, many new wiki editors are not aware that they cannot copy and paste a material from other wikis or other websites without giving attribution (quoting material). If a new editor were to do such a thing, he should be cordially warned and not blocked. Work with the editor, and avoid creating an intimidating or hostile environment. |
| | | | |
| | Editors should be blocked for actual behaviors and not merely suspicions. | | Editors should be blocked for actual behaviors and not merely suspicions. |