This Wikipedia page needs to be updated. The reason given is: to reflect the 2019 layout changes to the blocking form. Please help update this Wikipedia page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. |
Blocks exist to protect the project from harm, and reduce likely future problems. Appropriate use of a block can help prevent imminent problematic conduct and disruption to Wikipedia.
Do not block someone where you have, or may seem to have, a conflict of interest with regard to the editor in question or the topic in dispute – known as being "involved". This is generally construed very broadly by the community, to include current or past conflicts with an editor (or editors) and disputes on topics, regardless of the nature, age, or outcome of the dispute. However, issuing warnings, calm and reasonable discussion and explanation of those warnings, advice about communal norms, and suggestions on possible wordings and approaches, do not make an administrator 'involved'.
In cases which are straightforward, (e.g. blatant vandalism), the community has historically endorsed the obvious action of any administrator – even if involved – on the basis that any reasonable administrator would have probably come to the same conclusion. When in doubt, however, raise the matter at the relevant noticeboard and let other administrators take action, if appropriate.
Remember that even if you issue a block in a completely uninvolved, non-partisan manner and perfectly in-line with policy and past precedent, you are stopping another person from being able to contribute to the world's largest encyclopedia project, and they are unlikely to react to the block positively. If you have any doubts - don't block.
Common User block templates | |||
---|---|---|---|
Temporary | Indefinite | ||
Vandalism: | {{
uw-vblock}} |
{{
uw-voablock}}
| |
3RR: | {{
uw-3block}} |
— | |
Spamming: | {{
uw-sblock}} |
{{
Spamblock}}
| |
UserName: | — | {{
uw-ublock}}
| |
Legal threats: | — | {{
uw-lblock}}
| |
Sockpuppetry: | — | {{
uw-spoablock}}
| |
Harassment: | {{
uw-hblock}}
| ||
Generic Block: | {{
uw-block}} |
{{
uw-blockindef}}
|
One critical point to remember is that we block users to protect the encyclopedia from harm; blocks should not be punitive. Blocks are most often used for:
Blocking may be used in other situations (not just the above), where particular situations are addressed by more specific policies dealing with particular issues.
Blocks sometimes are used to allow discussions (such as AfD discussions) to proceed without interruption. The block length is usually based on how long you think the block needs to be in place to protect the encyclopedia. 31 hours is the standard duration for most blocks. Edit warring blocks (including WP:3RR) are usually 24 hours (some administrators prefer 31 hours). Registered sockpuppet accounts receive indefinite blocks, however, IP sockpuppet accounts only receive temporary blocks. Discussion blocks might last long enough to conclude the discussion. If you use Twinkle to block, it will automatically supply the standard durations based on the preset chosen.
Blocks are most often used after a user continues to vandalize despite repeated warnings. Such blocks generally are imposed when a user continues to vandalize after a final warning (corresponding to a level 4 warning template) but this is a guideline, not a hard and fast rule. Template warnings are often used but are not required. Single purpose accounts or vandalism-only accounts may warrant blocking with fewer warnings. In cases of gross or extreme vandalism a warning is not needed at all, such as in the case of promotion of hate and racism, or uploading shock images. Some users will deserve only one warning, others more warnings. Decide on the severity of the behavior and the likelihood of salvaging a good user. No hard and fast rule will do; use your good judgment.
You must not unblock any user who has been blocked as a CheckUser, Oversight, or Arbitration Committee action, as this can result in the removal of your admin rights, even for a first-time offense.
You may want to consider unblocking a user in a number of circumstances. These can include:
Administrators should not normally unblock users blocked in good faith by another administrator. If you plan on undoing another admin's block, ask them to consider unblocking first. The blocking administrator may have further information and history (e.g.,: action taken at WP:ANI or WP:AE) that is not immediately visible on an unblock request. If that is not possible (e.g.,: if the blocking admin has since retired) and there is good reason to unblock, notify the original blocking admin and consider posting a note at WP:AN to let other administrators review your intended actions. This will prevent wheel warring which would otherwise escalate into a dispute.
If you think the blocking administrator has a conflict of interest, you should still assume good faith that the block is correct, and discuss it at WP:AN.
Blocking a user is accomplished by filling out the blocking form. For the purposes of this guide we will use this form provided by the MediaWiki software. However, in practice you may more often use semi-automated tools for blocking such as Twinkle, which can make the process considerably easier, and add an appropriate message to the user's talk page that explains why they have been blocked, and how to appeal.
The blocking form can seem complicated at first with all of its checkboxes and options; however, once you understand what these options do, it is easy to determine which are needed and which aren't. Below is a step by step guide on how to make blocks to different groups of users. Follow the instructions through and then block the users as the guide says.
Yes, it's fine for you to block User:ThisIsaTest, User:192.0.2.16, User:2001:DB8:10:0:0:0:0:1 and User:Keegagan !!
Note: After you are done, please make sure to unblock the users/IPs that you have test-blocked and removed the block messages from their talk page so that these steps may be repeated by the next Admin.
User:ThisIsaTest has been causing massive disruption since he created his account 5 minutes ago. He has sequentially received the four warnings {{ uw-vandalism1}}, {{ uw-vandalism2}}, {{ uw-vandalism3}}, and {{ uw-vandalism4}} (which is more than adequate warning), yet he still continues his rampage. With his continued rampage after adequate warning, he needs to be blocked to stop any further disruption.
User:ThisIsaTest's block settings may need to be changed.
User:ThisIsaTest now says he is sorry – no, he says he is really sorry and has waited six months (per the standard offer) and you wish to unblock him:
For the purpose of these practice steps, please remove the {{ subst:uw-voablock}} post from ThisIsaTest's talk page.
User:192.0.2.16 has been causing massive disruption today and has received warnings from {{ uw-vandalism1}} to {{ uw-vandalism4}}, yet she still continues her rampage. The IP needs to be blocked to stop any further disruption.
User:192.0.2.16 now says she is sorry and you wish to unblock her:
For the purpose of these practice steps, please remove the {{ subst:uw-ablock}} from 192.0.2.16's talk page.
Sometimes disruption persists from a small range of IPs, where blocking each individually is ineffective. In such cases it may be feasible to perform a range block. This however should be avoided if at all possible, as it will cause collateral damage. It is suggested you discuss range blocks before making them, and if you aren't familiar with the Internet protocol suite and CIDR ranges, you shouldn't be making them.
Things to do before considering a range block:
Tools for computing the range of IPs:
Tools to check range contributions:
Blocking ranges works much the same way as you would block any IP, except you provide the CIDR range. If you feel a range block is warranted but are uncomfortable doing it yourself, you may wish to contact one of the admins in Category:Wikipedia administrators willing to make range blocks.
User:Keegagan is an inappropriate username due to it being too similar to an existing user. Assume that this is a clearly inappropriate username of the kind that can be blocked on sight by any administrator. To block,
User:Keegagan now says Keegagan is a family name and you wish to unblock him:
For the purpose of these practice steps, please remove the {{ subst:uw-uhblock-double}} post from Keegagan's talk page.
Partial blocks can prevent a user from:
To partially block a user, the following additional fields are used on the blocking form:
?ip=1.2.3.4
Range contributions are now supported in MediaWiki core. Simply enter the range at Special:Contributions.
You can also do a wildcard search (e.g. 83.217.178.*) using the Contribsrange gadget gadget. Enable "Allow /16, /24 and /27 – /32 CIDR ranges" at Special:Preferences#mw-prefsection-gadgets under "Advanced". Then type in any CIDR range into Special:Contribs.
This Wikipedia page needs to be updated. The reason given is: to reflect the 2019 layout changes to the blocking form. Please help update this Wikipedia page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. |
Blocks exist to protect the project from harm, and reduce likely future problems. Appropriate use of a block can help prevent imminent problematic conduct and disruption to Wikipedia.
Do not block someone where you have, or may seem to have, a conflict of interest with regard to the editor in question or the topic in dispute – known as being "involved". This is generally construed very broadly by the community, to include current or past conflicts with an editor (or editors) and disputes on topics, regardless of the nature, age, or outcome of the dispute. However, issuing warnings, calm and reasonable discussion and explanation of those warnings, advice about communal norms, and suggestions on possible wordings and approaches, do not make an administrator 'involved'.
In cases which are straightforward, (e.g. blatant vandalism), the community has historically endorsed the obvious action of any administrator – even if involved – on the basis that any reasonable administrator would have probably come to the same conclusion. When in doubt, however, raise the matter at the relevant noticeboard and let other administrators take action, if appropriate.
Remember that even if you issue a block in a completely uninvolved, non-partisan manner and perfectly in-line with policy and past precedent, you are stopping another person from being able to contribute to the world's largest encyclopedia project, and they are unlikely to react to the block positively. If you have any doubts - don't block.
Common User block templates | |||
---|---|---|---|
Temporary | Indefinite | ||
Vandalism: | {{
uw-vblock}} |
{{
uw-voablock}}
| |
3RR: | {{
uw-3block}} |
— | |
Spamming: | {{
uw-sblock}} |
{{
Spamblock}}
| |
UserName: | — | {{
uw-ublock}}
| |
Legal threats: | — | {{
uw-lblock}}
| |
Sockpuppetry: | — | {{
uw-spoablock}}
| |
Harassment: | {{
uw-hblock}}
| ||
Generic Block: | {{
uw-block}} |
{{
uw-blockindef}}
|
One critical point to remember is that we block users to protect the encyclopedia from harm; blocks should not be punitive. Blocks are most often used for:
Blocking may be used in other situations (not just the above), where particular situations are addressed by more specific policies dealing with particular issues.
Blocks sometimes are used to allow discussions (such as AfD discussions) to proceed without interruption. The block length is usually based on how long you think the block needs to be in place to protect the encyclopedia. 31 hours is the standard duration for most blocks. Edit warring blocks (including WP:3RR) are usually 24 hours (some administrators prefer 31 hours). Registered sockpuppet accounts receive indefinite blocks, however, IP sockpuppet accounts only receive temporary blocks. Discussion blocks might last long enough to conclude the discussion. If you use Twinkle to block, it will automatically supply the standard durations based on the preset chosen.
Blocks are most often used after a user continues to vandalize despite repeated warnings. Such blocks generally are imposed when a user continues to vandalize after a final warning (corresponding to a level 4 warning template) but this is a guideline, not a hard and fast rule. Template warnings are often used but are not required. Single purpose accounts or vandalism-only accounts may warrant blocking with fewer warnings. In cases of gross or extreme vandalism a warning is not needed at all, such as in the case of promotion of hate and racism, or uploading shock images. Some users will deserve only one warning, others more warnings. Decide on the severity of the behavior and the likelihood of salvaging a good user. No hard and fast rule will do; use your good judgment.
You must not unblock any user who has been blocked as a CheckUser, Oversight, or Arbitration Committee action, as this can result in the removal of your admin rights, even for a first-time offense.
You may want to consider unblocking a user in a number of circumstances. These can include:
Administrators should not normally unblock users blocked in good faith by another administrator. If you plan on undoing another admin's block, ask them to consider unblocking first. The blocking administrator may have further information and history (e.g.,: action taken at WP:ANI or WP:AE) that is not immediately visible on an unblock request. If that is not possible (e.g.,: if the blocking admin has since retired) and there is good reason to unblock, notify the original blocking admin and consider posting a note at WP:AN to let other administrators review your intended actions. This will prevent wheel warring which would otherwise escalate into a dispute.
If you think the blocking administrator has a conflict of interest, you should still assume good faith that the block is correct, and discuss it at WP:AN.
Blocking a user is accomplished by filling out the blocking form. For the purposes of this guide we will use this form provided by the MediaWiki software. However, in practice you may more often use semi-automated tools for blocking such as Twinkle, which can make the process considerably easier, and add an appropriate message to the user's talk page that explains why they have been blocked, and how to appeal.
The blocking form can seem complicated at first with all of its checkboxes and options; however, once you understand what these options do, it is easy to determine which are needed and which aren't. Below is a step by step guide on how to make blocks to different groups of users. Follow the instructions through and then block the users as the guide says.
Yes, it's fine for you to block User:ThisIsaTest, User:192.0.2.16, User:2001:DB8:10:0:0:0:0:1 and User:Keegagan !!
Note: After you are done, please make sure to unblock the users/IPs that you have test-blocked and removed the block messages from their talk page so that these steps may be repeated by the next Admin.
User:ThisIsaTest has been causing massive disruption since he created his account 5 minutes ago. He has sequentially received the four warnings {{ uw-vandalism1}}, {{ uw-vandalism2}}, {{ uw-vandalism3}}, and {{ uw-vandalism4}} (which is more than adequate warning), yet he still continues his rampage. With his continued rampage after adequate warning, he needs to be blocked to stop any further disruption.
User:ThisIsaTest's block settings may need to be changed.
User:ThisIsaTest now says he is sorry – no, he says he is really sorry and has waited six months (per the standard offer) and you wish to unblock him:
For the purpose of these practice steps, please remove the {{ subst:uw-voablock}} post from ThisIsaTest's talk page.
User:192.0.2.16 has been causing massive disruption today and has received warnings from {{ uw-vandalism1}} to {{ uw-vandalism4}}, yet she still continues her rampage. The IP needs to be blocked to stop any further disruption.
User:192.0.2.16 now says she is sorry and you wish to unblock her:
For the purpose of these practice steps, please remove the {{ subst:uw-ablock}} from 192.0.2.16's talk page.
Sometimes disruption persists from a small range of IPs, where blocking each individually is ineffective. In such cases it may be feasible to perform a range block. This however should be avoided if at all possible, as it will cause collateral damage. It is suggested you discuss range blocks before making them, and if you aren't familiar with the Internet protocol suite and CIDR ranges, you shouldn't be making them.
Things to do before considering a range block:
Tools for computing the range of IPs:
Tools to check range contributions:
Blocking ranges works much the same way as you would block any IP, except you provide the CIDR range. If you feel a range block is warranted but are uncomfortable doing it yourself, you may wish to contact one of the admins in Category:Wikipedia administrators willing to make range blocks.
User:Keegagan is an inappropriate username due to it being too similar to an existing user. Assume that this is a clearly inappropriate username of the kind that can be blocked on sight by any administrator. To block,
User:Keegagan now says Keegagan is a family name and you wish to unblock him:
For the purpose of these practice steps, please remove the {{ subst:uw-uhblock-double}} post from Keegagan's talk page.
Partial blocks can prevent a user from:
To partially block a user, the following additional fields are used on the blocking form:
?ip=1.2.3.4
Range contributions are now supported in MediaWiki core. Simply enter the range at Special:Contributions.
You can also do a wildcard search (e.g. 83.217.178.*) using the Contribsrange gadget gadget. Enable "Allow /16, /24 and /27 – /32 CIDR ranges" at Special:Preferences#mw-prefsection-gadgets under "Advanced". Then type in any CIDR range into Special:Contribs.