Misplaced Pages

:Blocking policy: Difference between revisions - Misplaced Pages

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 23:55, 4 October 2006 view sourceCrum375 (talk | contribs)Administrators23,963 edits Restore nutshells - please discuss in Template_talk:Policy_in_a_nutshell← Previous edit Revision as of 12:26, 5 October 2006 view source David Gerard (talk | contribs)Edit filter managers, Administrators213,122 edits replace with refactored form, per talk page discussionsNext edit →
Line 1: Line 1:
{{policy|]<br />]}} {{policy|]<br />]}}
{{policy in a nutshell|Editors can be blocked for a time by an administrator to protect Misplaced Pages and its editors from harm.}} {{policy in a nutshell|Editors can be blocked for a time by an administrator to protect Misplaced Pages and its editors from harm.|align=center}}
:''"WP:BP" redirects here. For the banning policy, see ] (]).''


'''Blocking''' is how a Misplaced Pages ] prevents a user or IP address/range from editing ].
:'''''A rewrite is proposed''' for this page. See ]. Discussion at ].''


'''Blocks are used to prevent damage or disruption to Misplaced Pages.''' They should not be used as a punitive measure.
'''Blocking''' is the means by which a Misplaced Pages ] prevents a user account or IP address/range from editing ]. Blocks are preventive rather than punitive measures used to prevent damage to Misplaced Pages by dealing with ] and enforcing ] and other Misplaced Pages policies. Block duration may vary, but normally lasts 24 hours unless specified otherwise, and in most instances a block can be lifted if the editor agrees to stop the damaging behavior.


Block duration varies (usually 24 hours at present), and a block may be lifted if the editor agrees to stop the damaging behavior. ], start by discussing it with the blocking admin. (''See'' ].).
All users may post block requests at ] or other venues listed below, which may result in quick action where credible evidence of policy violations is provided.


], begin by discussing it with the blocking admin. See ] for more information. Admins are never obliged to place a block. Admins and bureaucrats may also be blocked, with resulting ]. All users may request blocks at ] or other venues listed below. Include credible evidence of blockable offences. Admins are never obliged to place a block. Admins and bureaucrats may themselves be blocked, with resulting ].

''Note:'' When IP blocking, watch for ].


==When blocks may be used == ==When blocks may be used ==
The following section outlines the most common reasons a block might be used. All administrators should keep in mind that the block tool is intended to protect Misplaced Pages and its editors from harm. This document is not intended to be all-inclusive, nor should any omission be used to overturn a block. Every administrator should evaluate their blocks against the core values, policies and guidelines of Misplaced Pages and only use the tool when necesssary to protect the project and the people who contribute to its success.


=== Protection === === Protection ===
A user may be blocked when it is reasonably necessary to do so in order to protect the rights, property or safety of the Wikimedia Foundation, its users or the public. A user may be blocked when necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public. Examples include (but are not limited to):
*Personal attacks which place users in danger (See ])
*Persistent personal attacks
*Posting personal details
*Persistent copyright infringement


==== Personal attacks which place users in danger ==== ====Personal attacks that place users in danger====
Blocks may be imposed where threats have been made or actions performed (including actions outside the Misplaced Pages site) that expose Misplaced Pages editors to political, religious, or other persecution by government, their employer, or anyone else. Blocks of any length of time, including indefinite, may be applied.
{{main|Misplaced Pages:No personal attacks}}

Blocks may be imposed in instances where threats have been made or actions performed (including actions outside the Misplaced Pages site) which expose other Misplaced Pages editors to political, religious or other persecution by government, their employer or any others. In such a case a block of any length of time, including indefinite, may be applied immediately by any sysop upon discovery.


====Posting personal details==== ====Posting personal details====
Users who post what they believe are the personal details of other users without their consent may be blocked for any length of time, including indefinitely, depending on the severity of the incident, and whether the blocking admin feels the incident was isolated or is likely to be repeated. This applies whether the personal details are accurate or not. Nothing in this provision should be taken to apply to users with CheckUser access, who may make certain information available within the terms of the ]. Users who post what they believe are the personal details of other users without their consent may be blocked for any length of time, including indefinitely, depending on the severity of the incident, and whether the blocking admin feels the incident was isolated or is likely to be repeated. This applies whether the personal details are accurate or not. Nothing in this provision should be taken to apply to users with CheckUser access making information available within the terms of the ].

====Copyright infringement and plagiarism====
Inserting other people's work into Misplaced Pages without permission or attribution is unacceptable. ] and ] pose serious moral, legal, and reputation problems.

If there is a dispute in good faith over whether a work can be used, editors should err on the side of caution, and remove the disputed work from articles until the issue is settled. Editors who '''persistently''' insert disputed material, after having been warned, may be blocked to protect the project. In cases where an editor is acting in good faith, exercising caution with regard to the copyright issues, and there is no imminent legal threat, the editor should not be blocked.


=== Disruption === === Disruption ===
A user may be blocked when that user's conduct disrupts the project. Broadly speaking, this means that their conduct is inconsistent with a civil, collegial atmosphere and interferes with the process of editors working together harmoniously to create an encyclopedia. A user may be blocked when their conduct severely disrupts the project &mdash; their conduct is inconsistent with a civil, collegial atmosphere and interferes with the process of editors working together harmoniously to create an encyclopedia.


Disagreements over content or policy are not disruption, but rather part of the normal functioning of Misplaced Pages and should be handled through ] procedures. Blocks for disruption should only be placed when a user is in some way making it difficult for others to contribute to Misplaced Pages.
Sysops may block IP addresses or usernames that disrupt the normal functioning of Misplaced Pages, or pose any kind of threat to it. Such disruption may include (but is not limited to) changing other users' signed comments, making deliberately misleading edits, ], excessive personal attacks, and inserting material that may be defamatory. Users will normally be warned before they are blocked.


Sysops may block IP addresses or usernames that disrupt the normal functioning of Misplaced Pages, or pose a sufficiently severe threat to it. Examples include (but are not limited to):
Sysops may also block new user accounts that make lots of disruptive edits. Reincarnations of blocked disruptive users are likely to be re-blocked, particularly if they edit in a way that suggests they are likely to continue being disruptive.
*]
*Excessive reverts (])
*]
*Abusive ] accounts
*"Public" accounts, where the password is publicly available or shared with a large group
*]
*Disrupting ]; for example, by repeatedly posting negative unsourced material
*] must have prior approval on ] and may be blocked if an admin thinks they are malfunctioning in a damaging way


Blocks for gross incivility are controversial; "cool-down" blocks are ''very'' controversial. Consider whether a 1-hour block will result in 2 months' drama. ''See'' ].
Note that ordinary disagreements over content are not disruption, but rather part of the normal functioning of Misplaced Pages and should be handled through ] procedures. The exception is when there is consensus that we are dealing with a ]. Blocks for disruption should only be placed when a user is in some way making it difficult for others to contribute to Misplaced Pages.


Obvious ]s and users who aggressively and repeatedly violate fundamental policies may be blocked if there is a consensus among uninvolved users that it is necessary. Such persons should be dealt with kindly and patiently, but should be prevented from wreaking havoc over the period of weeks or months it would take to process an obvious Arbitration request. Remember to note the case on ]. Be kind.
====Disruptive editing, per se====
{{main|Misplaced Pages:Disruptive editing}}
Obvious ]s and users who aggressively and repeatedly violate ] may be blocked if there is a consensus among uninvolved users that it is necessary. Such persons should be dealt with kindly and patiently, but should be prevented from wreaking havoc over the period of weeks or months it would take to process an obviously righteous ].


====Vandalism==== === Bans ===
{{main|Misplaced Pages:Vandalism}} {{main|Misplaced Pages:Banning policy}}
''Report at ]''<br/>


Banned users are typically blocked from editing all or parts of Misplaced Pages. They may be banned by the ], by ] or by the ] ].
Sysops may block IP addresses whose users vandalise Misplaced Pages.


Users may also be banned by community consensus &mdash; when a user exhausts the community's patience to the point of being blocked and none of English Misplaced Pages's ~1000 admins will unblock.
==== Excessive reverts ====
''Report at ]''<br/>


Community bans ''must'' be supported by a strong widespread consensus. Before blocking someone for this, you should be very sure there is or would be widespread community support for the block; note it with reasons on ] for others to sanity-check. Such users can be considered banned and must be listed on ] (under "Community").
Sysops may block users for ]ring. As a rule of thumb, this happens when an editor reverts for the fourth time in a 24-hour period (see ]). Where multiple parties violate the rule, sysops will treat all sides equally.


====Biographies of living persons==== === Evasion of blocks ===
A blocked user cannot edit any pages other than their own talk page. Admins may restart the blocks of users who intentionally evade a block, and may extend the original blocks if the user commits further blockable acts. Accounts and IPs used in evading a block may also be blocked.
{{see|Misplaced Pages:Biographies of living persons}}
Editors who repeatedly insert critical material into the biography of a living person (or its talk page), or into a section about a living person in another article (or its talk page), may be blocked under the disruption provision of this policy if, in the opinion of the blocking admin, the material is ], or ], and may constitute ]. Blocks made for this reason are designed to keep the material off the page until it is written and sourced in accordance with the content policies, including ], and should therefore be kept short in the first instance. Repeated infractions should attract longer blocks. Warning and block templates may be placed on the user's talk page: {{tl|blp1}}, {{tl|blp2}}, and {{tl|blp3}}. See the section on ] above.


Edits made by blocked users while blocked ''may'' be reverted. (Many admins revert all edits from the user and re-make the good edits under their own name, to avoid confusing other admins who may be monitoring the same user.)
==== Usernames ====
According to our ], inflammatory, deliberately confusing, and other inappropriate usernames are not allowed, and in certain circumstances, sysops may block accounts with such usernames. Usernames that are designed to impersonate legitimate users will be blocked immediately and indefinitely.


=== Death ===

The account(s) of users who are conclusively known to have died may be blocked indefinitely to prevent their use by other parties.

====Sockpuppet accounts====
Sysops may block abusive ]s (e.g. used to circumvent blocks or create an illusion of consensus) indefinitely.

This applies to "reincarnations" of existing banned users too.

==== "Public" accounts ====
It is Misplaced Pages policy that accounts that have one specific name, but were created for use by multiple people, are not acceptable. Examples include any account where the owner posts the password for public use. These may be blocked on sight indefinitely.

==== Bots ====
] must have prior approval on ], and must follow certain minimum standards. In any case, sysops may block on sight any bot that appears to be out of control.

==== Anonymous and open proxies ====
{{main|Misplaced Pages:No open proxies}}

Administrators are permitted and encouraged to IP-block anonymous proxies indefinitely.

=== Bans ===
{{main|Misplaced Pages:Banning policy}}

Users that have been banned are typically blocked from editing Misplaced Pages. Such bans may occur as the result of community consensus that the user should be banned, ruling by the ], ruling by ], or ruling by the ] ].

==== Users who exhaust the community's patience ====
There have been situations where a user has exhausted the community's patience to the point where he or she finds themselves blocked. Administrators who block in these cases should be sure that there is widespread community support for the block, and should note the block on ] as part of the review process. With such support, the user is considered banned and must be listed on ] (under "Community"). Community bans ''must'' be supported by a strong consensus and should never be enacted based on agreement between a handful of admins or users.

=== Evasion of blocks ===
While blocked, a user is not permitted to edit any pages other than his or her own talk page. ] may reset the blocks of users who intentionally use various tactics to evade a block, and may extend the original blocks if the user commits further blockable acts. Accounts and IPs used in evading a block may also be blocked appropriately. Edits made by blocked users while blocked ''may'' be reverted.


== Effects of being blocked == == Effects of being blocked ==
Blocked users and IP addresses can still see all Misplaced Pages pages, but the "Edit this page" link brings up a "]" page which explains the reason behind the block and gives information on how to request unblocking. This page includes the "reason" message supplied by the administrator who placed the block. Links and template includes all work as normal in the "reason" section. Blocked users are also prevented from moving pages or uploading files. Blocked users and IP addresses can still see all Misplaced Pages pages, but the "Edit this page" link brings up a "]" page with the reason behind the block (as entered by the blocking admin) and how to request unblocking. Links and template includes all work as normal in the "reason" section. Blocked users are also prevented from moving pages or uploading files.


When a blocked user attempts to edit, their IP is "autoblocked", so that the user may not make the same edit anonymously or under a different username. Autoblocks expire after 24 hours &mdash; when a username is blocked indefinitely, their IP will be automatically unblocked 24 hours after he or she last attempted to edit a page.
The duration of the block depends on the expiration time that was entered at the time of the block, which may be "indefinite" or "infinite" (i.e., until explicitly unblocked).

When a blocked user attempts to edit, the IP from which he or she is editing is "autoblocked", so that the user may not make the same edit anonymously or under a different user name. There is an internal autoblock expiry time variable, which is set to 24 hours, meaning that when a username is blocked indefinitely, their IP will be automatically unblocked 24 hours after he or she last accessed a page.


For admins, being blocked also restricts their ability to use rollback, to delete and undelete pages, and to protect and unprotect pages. They can still add and remove blocks, and bureaucrats can still make someone a sysop. For admins, being blocked also restricts their ability to use rollback, to delete and undelete pages, and to protect and unprotect pages. They can still add and remove blocks, and bureaucrats can still make someone a sysop.


== Accidental blocks == == Accidental blocks ==
Occasionally, users with dynamic IPs will find that they have been blocked accidentally, because their present IP was previously used by a vandal or hard-banned user. These blocks will disappear if IP change can be forced. If that is not possible, the block should be reported to the nearest friendly sysop via email&mdash;see the ] for some likely candidates. Users with ] will occasionally find that they have been blocked accidentally, because their IP or range was previously used by a vandal or hard-banned user. These blocks may disappear if IP change can be forced. If that is not possible, the block should be reported to the blocking admin and/or the nearest friendly sysop via email &mdash; see the ] for some likely candidates. IRC #wikipedia may also be useful.

Admins can often let the accidentally-blocked editor through by undoing only the autoblocking of the IP. (Don't forget to let the blocking admin know of the collateral damage.)


Users who act so as to impersonate a previously banned user, to impersonate a known vandal, or to pretend to be engaging in vandalism, are also likely to be blocked. To avoid this problem, do not act in this way. It is good practice to edit so as to demonstrate your trustworthiness, not to put up a façade of untrustworthiness. Users who act so as to impersonate a previously banned user, to impersonate a known vandal, or to pretend to be engaging in vandalism, are also likely to be blocked. To avoid this problem, don't do this. Edit so as to demonstrate your trustworthiness, not to put up a façade of untrustworthiness.


==When blocking may not be used== ==When blocking may not be used==
Use of blocks to gain an advantage in a content dispute is strictly prohibited. That is, sysops must not block editors with whom they are currently engaged in a content dispute.


Blocking to gain an advantage in a content dispute is strictly prohibited. Sysops must not block editors with whom they are currently engaged in a content dispute. If in doubt, report the problem to other admins to act on. (You may be wrong!)
Generally, caution should be exercised before blocking users who may be acting in good faith.

Caution should be exercised before blocking users who may be acting in good faith.


Blocking to enforce a ] or departure is specifically prohibited. Sysops also should not block themselves for testing unless ] is disabled, or the sysop is using a static IP, as the resulting autoblock may extend to other users. Blocking to enforce a ] or departure is specifically prohibited. Sysops also should not block themselves for testing unless ] is disabled, or the sysop is using a static IP, as the resulting autoblock may extend to other users.
Line 113: Line 89:


=== How to block === === How to block ===
Sysops may go to ] and select the "Block a user/IP address" link. This takes them to ], which has further instructions. Special:Blockip is also accessible via the link that appears next to each non-logged in user on ]. Go to ] and then the "Block a user/IP address" link. This goes to ]. Special:Blockip is also accessible via the link that appears next to each non-logged in user on ].


The "reason" that the administrator fills in will be displayed to the blocked user when he attempts to edit, as well as appearing in the ] and the ]. If it is not for an obvious reason, or if more than one line is needed to explain the block, the administrator may record the block at ]. The "reason" that the administrator fills in will be displayed to the blocked user when he attempts to edit, as well as appearing in the ] and the ]. If it is not for an obvious reason, or if more than one line is needed to explain the block, the administrator may record the block at ] and/or ].


Users should be notified of blocks on their talk pages. That way, other editors will be aware that the user is blocked, and will not expect responses to talk page comments. Users should be notified of blocks on their talk pages. That way, other editors will be aware that the user is blocked, and will not expect responses to talk page comments.
Line 121: Line 97:
====Options for IP blocks==== ====Options for IP blocks====


There are two options available at ] that can affect the operation of IP blocks. '''Block anonymous users only''' prevents anonymous users from the target IP address from editing, but allows registered users to edit. '''Prevent account creation''' prevents new accounts from being registered from the target IP address. These options have no effect on username blocks. '''Block anonymous users only''' prevents anonymous users from the target IP address from editing, but allows registered users to edit. '''Prevent account creation''' prevents new accounts from being registered from the target IP address. These options have no effect on username blocks.


In some cases, an IP may be shared by administrators who request they be notified before blocks are placed on them (so that they may finish any administrative work they are doing). For this reason, it is advisable to check the user talk page of the IP where any such request will be listed. In this situation it may be advisable to select the '''block anonymous users only'''. In some cases, an IP may be shared by administrators who want to be notified before blocks are placed on them (so that they may finish any administrative work). As such, you may want to check the IP's user page or talk page and select "block anonymous users only".


=== Expiry times and application === === Guide to blocking times ===

Expiry times are entered in the GNU standard format, which is described in the . Alternatively, a block may be "indefinite" or "infinite", meaning the block is permanent, until a sysop explicitly unblocks the account.
The block time can be selected from the menu, or entered in the . Alternatively, a block may be "indefinite" or "infinite", meaning the block is permanent, until a sysop explicitly unblocks the account.


If no expiry time is entered, an error message will be displayed. If no expiry time is entered, an error message will be displayed.


The times below are convention, based on protection of Misplaced Pages rather than punishment of the offender. They are guidelines &mdash; if you have done something clearly blockable, demanding the blocking admin's head for giving you 31 hours instead of 24 is unlikely to be taken seriously.
* '''Vandalism''' &mdash; For dynamic IPs, such blocks should last up to 24 hours. Normally, AOL IPs should be blocked for about 15 minutes, then 1-3 hours, and typically topping out at 24 hours. Because of the great ] caused by range blocks, they should be confined to several minutes. For static IPs, such blocks should initially last 24 hours, and should increase gradually upon resumption of vandalism; eventually repeat violators may be blocked indefinitely, but such blocks should be issued with discretion. Logged-in users that repeatedly vandalise may also be blocked for the same time periods. Blocks should not be used against isolated incidents of vandalism.
* '''Excessive reverting''' &mdash; It is helpful to leave a notice of the block, with links to the differences that demonstrate the violation, on the user's talk page.
* '''Disruption''' &mdash; For dynamic IPs, such blocks should last 24 hours. For static IPs and user names, such blocks should initially last 24 hours, but repeat violators may be blocked for increasing lengths of time. New accounts may be blocked for any length of time or permanently, and ] that were created to violate Misplaced Pages policy should be blocked permanently. However, indefinite blocks should not be used against isolated incidents of disruption from IP addresses nor against user accounts that make a mixture of disruptive and useful edits.
* '''Usernames''' &mdash; The IP address of these users should be left autoblocked. Accounts and IP addresses that illegitimately use another account's name in the signature should be warned first, and then can be blocked. Please be sure that the account is a ''malicious'' impersonator before blocking it; someone might choose a name similar to that of another user without any ill intent. If they are making legitimate edits, they should be told of the possible confusion and encouraged to change usernames. Sysops can force a name change by blocking the username with an expiry time of infinite. The blocking sysop should include ] in the block message (by writing {{tl|UsernameBlock}} in the "reason" field), along with a link to the RfC or user talk page where the matter was discussed. If a user page has already been created, any user may add an explanation of why the user was blocked and a link to the ] page on the blocked user's userpage. It is not advisable to create user pages or talk pages for users with offensive usernames.
*'''Public accounts''' &mdash; These should be blocked with a block message pointing out that public accounts are not needed. As an alternative, when confirming that the password is public, it is quite simple and often creates less fuss to just go into ] and change the password. This makes the password no longer public, and can also be done by anyone, not just an administrator.
*'''Bots''' &mdash; Initial blocks should last 24 hours, which should be sufficient time to allow the operator of the bot to respond.
*'''Personal attacks which place users in danger''' &mdash; Sysops applying such sanctions should confidentially notify the members of the Arbitration Committee and Jimbo Wales of what they have done and why.


* '''Disruption''' &mdash; Dynamic IPs: up to 24 hours. Static IPs and logged-in users: start at 24 hours, increase gradually if it starts again. Blocks less than 24 hours, often known as '''cool-down blocks''' are more likely to be controversial the shorter they are. Indefinite blocks should not be used against isolated incidents of disruption from IP addresses, nor at first against user accounts that make a mixture of disruptive and useful edits. Some types of disruption have more established guidelines:
=== Range blocks ===
:* '''Vandalism''' &mdash; Blocks should not be used against isolated incidents of vandalism. Dynamic IPs: up to 24 hours. AOL IPs and range blocks: about 15 minutes, then 1-3 hours, and 24 at most, to avoid ]. Static IPs and logged-in users: start at 24 hours, increase gradually if it starts again; persistent violators may be blocked indefinitely, but use discretion.
:* '''Excessive reverting''' (]) &mdash; It is helpful to leave a notice of the block on the user's talk page.
:* '''Inappropriate Usernames''' &mdash; IP address should be left autoblocked. Cases of impersonation may not be malicious, consider warning a user before blocking and remember to include {{Template|UsernameBlock}} in the "reason" field with a link to any discussion.
:* '''Abusive Sockpuppets''' &mdash; New accounts may be blocked for any length of time or permanently; ] for violating policy should be blocked permanently.
:*'''Public accounts''' &mdash; These should be blocked with a block message pointing out that public accounts are not needed.
:*'''Bots''' &mdash; Initial blocks should last 24 hours, which should be sufficient time to allow the operator of the bot to respond to a talk page message.
:*'''Personal attacks which place users in danger''' &mdash; Sysops applying such sanctions should confidentially notify the members of the Arbitration Committee (arbcom-l@wikipedia.org) and Jimbo Wales (jwales@wikia.com) of what they have done and why. See also ].


=== Range blocks ===
Range blocks are sometimes used when a vandal or disruptive user has been IP blocked on several occasions but responds by using a different IP address. In most cases, range blocks will affect at least some legitimate users. Therefore, range blocks should only be used when the disruptive behavior is frequent and severe enough to make other methods ineffective. This is a matter of judgement, and the likely number of legitimate users that might be affected should be considered.


These are sometimes used when a problem user responds to several IP blocks by changing IP address. They will affect at least some legitimate users, so should only be used when the disruptive behavior is frequent and severe enough to make other methods ineffective. Use careful judgement and make them as brief as possible.
When used, range blocks should be as brief as possible.


The range block feature is difficult to use correctly because it requires an understanding of binary arithmetic. It has certain limitations inherent in its implementation, requiring the starting and ending addresses to be an exact multiple of the distance between them, which must be a power of two. For details, see ]. You need some knowledge of how networks and IP numbering work, and of binary arithmetic. If you don't, many other admins do - ask on ] or IRC. See ].


=== Unblocking === === Unblocking ===
Line 150: Line 128:
] contains a list of all currently blocked users and IPs. Sysops will see a link to (<font color=blue></font>) next to each user. After clicking this, you should type in the reason that you are unblocking the user and then click the ''Unblock this address'' button. ] contains a list of all currently blocked users and IPs. Sysops will see a link to (<font color=blue></font>) next to each user. After clicking this, you should type in the reason that you are unblocking the user and then click the ''Unblock this address'' button.


Sysops are technically able to unblock themselves by following this procedure but should absolutely ''not'' do so, except if they were autoblocked as a result of a block on some other user (or bot) that they share an IP with. Otherwise, if an admin feels they were not blocked for a valid reason, they should contact the blocking admin, another admin, or the mailing list and ask to be unblocked. Self-unblocking is treated extremely seriously by the community and has resulted in several users losing their sysop privileges. Sysops are technically able to unblock themselves by following this procedure but should absolutely ''not'' do so unless they were autoblocked as a result of a block on some other user (or bot) that they share an IP with. Otherwise, if an admin feels they were not blocked for a valid reason, they should contact the blocking admin, another admin, or the mailing list and ask to be unblocked. Self-unblocking without convincingly good reason has resulted in several users losing their sysop privileges.


=== If you disagree with a block === === If you disagree with a block ===
If you disagree with a block placed by another admin, do not unblock without first contacting the blocking admin and discussing the matter. If the blocking admin is unavailable for comment a discussion on ] is recommended instead. Blocked users commonly e-mail several admins claiming to be the victims of injustice, and because it is not always obvious from the blocked user's contributions what the problem was, it is a matter of courtesy and common sense to consult the blocking admin if they are available. If you disagree with a block placed by another admin, do not unblock without first attempting to contact the blocking admin and discussing the matter. If the blocking admin is unavailable for comment a discussion on ] is recommended. Blocked users commonly e-mail several admins claiming to be the victims of injustice, and because it is not always obvious from the blocked user's contributions what the problem was, it is a matter of courtesy and common sense to consult the blocking admin if they are available.


Exceptions to this would be where an unambiguous error has been made (not a judgment call) and the blocking admin is not online: for example, if a user was blocked for 3RR, but there were clearly only three reverts. If the blocking admin is not available, you should notify the blocking admin on his or her talk page and possibly a note to ]. Exceptions to this would be where an unambiguous error has been made (not a judgment call) and the blocking admin is not online: for example, if a user was blocked for 3RR, but there were clearly only three reverts. If the blocking admin is not available, you should notify the blocking admin on his or her talk page and possibly a note to ].


=== Controversial blocks === === Controversial blocks ===
Blocks may be damaging when consensus proves elusive. Examples include:

* blocks of logged-in users with a substantial history of valid contributions, regardless of the reason for the block
While blocking IP addresses responsible for anonymous, clear-cut vandalism is routine, many other uses of IP and username blocks are contentious. Where consensus proves elusive, such blocks are damaging to the community.

Blocks that may be controversial are:
* blocks of suspected "sock puppets" or "reincarnations" of banned users
* blocks of logged-in users with a substantial history of valid contributions, regardless of the reasoning for the block
* blocks made under the ] provision of the blocking policy.
* blocks that, while possibly wise, lack policy basis. * blocks that, while possibly wise, lack policy basis.
* short term or '''cool-down''' blocks.


Once you are convinced that a block is warranted, the recommended procedure for controversial blocks is: Once you are convinced that a block is warranted, the recommended procedure for controversial blocks is:
Line 171: Line 145:
# Check the facts with care. # Check the facts with care.
# Reread appropriate parts of Misplaced Pages:Blocking policy. # Reread appropriate parts of Misplaced Pages:Blocking policy.
# If possible, contact other administrators informally to be sure there are others who agree with your reasoning. The administrators' noticeboard, ] and email are effective tools for this. # If possible, contact other administrators to sanity-check your reasoning, preferably on ].
# Place the block, exercising due care in the wording of the "reason" message, and include a link to the user page of the user being blocked. # Place the block, wording the "reason" message with care and without jargon, and include a link to the user page of the user being blocked.
# Place a notice of the block on the ] page of the affected user, with additional rationale, outlining the facts and the part of the blocking policy you feel applies. # Place a notice of the block on the ] page of the affected user, with additional rationale, outlining the facts and the part of the blocking policy you feel applies.
# Be willing to discuss the block with other Wikipedians. # Stay around to discuss the block with other Wikipedians.
# If an act or acts of disruption do not warrant a 24-hour block, consider a warning or posting to ] before issuing a short term block. (Someone may well block them longer than you would have!)


], in which a user is repeatedly blocked and unblocked, are extremely harmful. They are a source of frustration and disappointment to many seasoned Wikipedians and tend to encourage further bad behavior on the part of the blocked user. Avoid them. If you disagree with a block, discuss the matter with the blocking admin and others, and try to reach a consensus, rather than unblocking. Bear in mind that the blocking admin is likely to know more about the background to the situation than you do. ], in which a user is repeatedly blocked and unblocked, are extremely harmful. They frustrate and disappoint seasoned Wikipedians and encourage further bad behavior from the blocked user. If you disagree with a block, discuss the matter with the blocking admin and others, and try to reach a consensus, rather than unblocking &mdash; the blocking admin is likely to know more about the background of the situation than you do.


==See also== ==See also==
Line 186: Line 161:
* ], category containing user block templates * ], category containing user block templates
* ] * ]
* ], a particularly stupid arbitration case after which several admins were deadminned. Wheel wars are bad.


] ]

Revision as of 12:26, 5 October 2006

This page documents an English Misplaced Pages policy.It describes a widely accepted standard that editors should normally follow, though exceptions may apply. Changes made to it should reflect consensus.Shortcut
  • ]
This page in a nutshell: Editors can be blocked for a time by an administrator to protect Misplaced Pages and its editors from harm.

Blocking is how a Misplaced Pages administrator prevents a user or IP address/range from editing Misplaced Pages.

Blocks are used to prevent damage or disruption to Misplaced Pages. They should not be used as a punitive measure.

Block duration varies (usually 24 hours at present), and a block may be lifted if the editor agrees to stop the damaging behavior. If you disagree with a block, start by discussing it with the blocking admin. (See Appealing a block.).

All users may request blocks at ANI or other venues listed below. Include credible evidence of blockable offences. Admins are never obliged to place a block. Admins and bureaucrats may themselves be blocked, with resulting effects on their other powers.

Note: When IP blocking, watch for sensitive IP addresses.

When blocks may be used

The following section outlines the most common reasons a block might be used. All administrators should keep in mind that the block tool is intended to protect Misplaced Pages and its editors from harm. This document is not intended to be all-inclusive, nor should any omission be used to overturn a block. Every administrator should evaluate their blocks against the core values, policies and guidelines of Misplaced Pages and only use the tool when necesssary to protect the project and the people who contribute to its success.

Protection

A user may be blocked when necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public. Examples include (but are not limited to):

Personal attacks that place users in danger

Blocks may be imposed where threats have been made or actions performed (including actions outside the Misplaced Pages site) that expose Misplaced Pages editors to political, religious, or other persecution by government, their employer, or anyone else. Blocks of any length of time, including indefinite, may be applied.

Posting personal details

Users who post what they believe are the personal details of other users without their consent may be blocked for any length of time, including indefinitely, depending on the severity of the incident, and whether the blocking admin feels the incident was isolated or is likely to be repeated. This applies whether the personal details are accurate or not. Nothing in this provision should be taken to apply to users with CheckUser access making information available within the terms of the CheckUser policy.

Disruption

A user may be blocked when their conduct severely disrupts the project — their conduct is inconsistent with a civil, collegial atmosphere and interferes with the process of editors working together harmoniously to create an encyclopedia.

Disagreements over content or policy are not disruption, but rather part of the normal functioning of Misplaced Pages and should be handled through dispute resolution procedures. Blocks for disruption should only be placed when a user is in some way making it difficult for others to contribute to Misplaced Pages.

Sysops may block IP addresses or usernames that disrupt the normal functioning of Misplaced Pages, or pose a sufficiently severe threat to it. Examples include (but are not limited to):

Blocks for gross incivility are controversial; "cool-down" blocks are very controversial. Consider whether a 1-hour block will result in 2 months' drama. See Misplaced Pages:Disruptive editing.

Obvious cranks and users who aggressively and repeatedly violate fundamental policies may be blocked if there is a consensus among uninvolved users that it is necessary. Such persons should be dealt with kindly and patiently, but should be prevented from wreaking havoc over the period of weeks or months it would take to process an obvious Arbitration request. Remember to note the case on WP:ANI. Be kind.

Bans

Main page: Misplaced Pages:Banning policy

Banned users are typically blocked from editing all or parts of Misplaced Pages. They may be banned by the Arbitration Committee, by Jimbo Wales or by the Wikimedia Board of Trustees.

Users may also be banned by community consensus — when a user exhausts the community's patience to the point of being blocked and none of English Misplaced Pages's ~1000 admins will unblock.

Community bans must be supported by a strong widespread consensus. Before blocking someone for this, you should be very sure there is or would be widespread community support for the block; note it with reasons on WP:ANI for others to sanity-check. Such users can be considered banned and must be listed on Misplaced Pages:List of banned users (under "Community").

Evasion of blocks

A blocked user cannot edit any pages other than their own talk page. Admins may restart the blocks of users who intentionally evade a block, and may extend the original blocks if the user commits further blockable acts. Accounts and IPs used in evading a block may also be blocked.

Edits made by blocked users while blocked may be reverted. (Many admins revert all edits from the user and re-make the good edits under their own name, to avoid confusing other admins who may be monitoring the same user.)

Death

The account(s) of users who are conclusively known to have died may be blocked indefinitely to prevent their use by other parties.

Effects of being blocked

Blocked users and IP addresses can still see all Misplaced Pages pages, but the "Edit this page" link brings up a "User is blocked" page with the reason behind the block (as entered by the blocking admin) and how to request unblocking. Links and template includes all work as normal in the "reason" section. Blocked users are also prevented from moving pages or uploading files.

When a blocked user attempts to edit, their IP is "autoblocked", so that the user may not make the same edit anonymously or under a different username. Autoblocks expire after 24 hours — when a username is blocked indefinitely, their IP will be automatically unblocked 24 hours after he or she last attempted to edit a page.

For admins, being blocked also restricts their ability to use rollback, to delete and undelete pages, and to protect and unprotect pages. They can still add and remove blocks, and bureaucrats can still make someone a sysop.

Accidental blocks

Users with dynamic IPs will occasionally find that they have been blocked accidentally, because their IP or range was previously used by a vandal or hard-banned user. These blocks may disappear if IP change can be forced. If that is not possible, the block should be reported to the blocking admin and/or the nearest friendly sysop via email — see the list of administrators for some likely candidates. IRC #wikipedia may also be useful.

Admins can often let the accidentally-blocked editor through by undoing only the autoblocking of the IP. (Don't forget to let the blocking admin know of the collateral damage.)

Users who act so as to impersonate a previously banned user, to impersonate a known vandal, or to pretend to be engaging in vandalism, are also likely to be blocked. To avoid this problem, don't do this. Edit so as to demonstrate your trustworthiness, not to put up a façade of untrustworthiness.

When blocking may not be used

Blocking to gain an advantage in a content dispute is strictly prohibited. Sysops must not block editors with whom they are currently engaged in a content dispute. If in doubt, report the problem to other admins to act on. (You may be wrong!)

Caution should be exercised before blocking users who may be acting in good faith.

Blocking to enforce a Wikiholiday or departure is specifically prohibited. Sysops also should not block themselves for testing unless "autoblock" is disabled, or the sysop is using a static IP, as the resulting autoblock may extend to other users.

Instructions to admins

How to block

Go to Special pages and then the "Block a user/IP address" link. This goes to Special:Blockip. Special:Blockip is also accessible via the link that appears next to each non-logged in user on recent changes.

The "reason" that the administrator fills in will be displayed to the blocked user when he attempts to edit, as well as appearing in the block log and the block list. If it is not for an obvious reason, or if more than one line is needed to explain the block, the administrator may record the block at Misplaced Pages:Policy enforcement and/or WP:ANI.

Users should be notified of blocks on their talk pages. That way, other editors will be aware that the user is blocked, and will not expect responses to talk page comments.

Options for IP blocks

Block anonymous users only prevents anonymous users from the target IP address from editing, but allows registered users to edit. Prevent account creation prevents new accounts from being registered from the target IP address. These options have no effect on username blocks.

In some cases, an IP may be shared by administrators who want to be notified before blocks are placed on them (so that they may finish any administrative work). As such, you may want to check the IP's user page or talk page and select "block anonymous users only".

Guide to blocking times

The block time can be selected from the menu, or entered in the GNU standard format. Alternatively, a block may be "indefinite" or "infinite", meaning the block is permanent, until a sysop explicitly unblocks the account.

If no expiry time is entered, an error message will be displayed.

The times below are convention, based on protection of Misplaced Pages rather than punishment of the offender. They are guidelines — if you have done something clearly blockable, demanding the blocking admin's head for giving you 31 hours instead of 24 is unlikely to be taken seriously.

  • Disruption — Dynamic IPs: up to 24 hours. Static IPs and logged-in users: start at 24 hours, increase gradually if it starts again. Blocks less than 24 hours, often known as cool-down blocks are more likely to be controversial the shorter they are. Indefinite blocks should not be used against isolated incidents of disruption from IP addresses, nor at first against user accounts that make a mixture of disruptive and useful edits. Some types of disruption have more established guidelines:
  • Vandalism — Blocks should not be used against isolated incidents of vandalism. Dynamic IPs: up to 24 hours. AOL IPs and range blocks: about 15 minutes, then 1-3 hours, and 24 at most, to avoid collateral damage. Static IPs and logged-in users: start at 24 hours, increase gradually if it starts again; persistent violators may be blocked indefinitely, but use discretion.
  • Excessive reverting (3RR) — It is helpful to leave a notice of the block on the user's talk page.
  • Inappropriate Usernames — IP address should be left autoblocked. Cases of impersonation may not be malicious, consider warning a user before blocking and remember to include {{UsernameBlock}} in the "reason" field with a link to any discussion.
  • Abusive Sockpuppets — New accounts may be blocked for any length of time or permanently; sockpuppets for violating policy should be blocked permanently.
  • Public accounts — These should be blocked with a block message pointing out that public accounts are not needed.
  • Bots — Initial blocks should last 24 hours, which should be sufficient time to allow the operator of the bot to respond to a talk page message.
  • Personal attacks which place users in danger — Sysops applying such sanctions should confidentially notify the members of the Arbitration Committee (arbcom-l@wikipedia.org) and Jimbo Wales (jwales@wikia.com) of what they have done and why. See also Misplaced Pages:Oversight.

Range blocks

These are sometimes used when a problem user responds to several IP blocks by changing IP address. They will affect at least some legitimate users, so should only be used when the disruptive behavior is frequent and severe enough to make other methods ineffective. Use careful judgement and make them as brief as possible.

You need some knowledge of how networks and IP numbering work, and of binary arithmetic. If you don't, many other admins do - ask on ANI or IRC. See Range blocks.

Unblocking

Special:Ipblocklist contains a list of all currently blocked users and IPs. Sysops will see a link to (unblock) next to each user. After clicking this, you should type in the reason that you are unblocking the user and then click the Unblock this address button.

Sysops are technically able to unblock themselves by following this procedure but should absolutely not do so unless they were autoblocked as a result of a block on some other user (or bot) that they share an IP with. Otherwise, if an admin feels they were not blocked for a valid reason, they should contact the blocking admin, another admin, or the mailing list and ask to be unblocked. Self-unblocking without convincingly good reason has resulted in several users losing their sysop privileges.

If you disagree with a block

If you disagree with a block placed by another admin, do not unblock without first attempting to contact the blocking admin and discussing the matter. If the blocking admin is unavailable for comment a discussion on WP:AN/I is recommended. Blocked users commonly e-mail several admins claiming to be the victims of injustice, and because it is not always obvious from the blocked user's contributions what the problem was, it is a matter of courtesy and common sense to consult the blocking admin if they are available.

Exceptions to this would be where an unambiguous error has been made (not a judgment call) and the blocking admin is not online: for example, if a user was blocked for 3RR, but there were clearly only three reverts. If the blocking admin is not available, you should notify the blocking admin on his or her talk page and possibly a note to WP:AN/I.

Controversial blocks

Blocks may be damaging when consensus proves elusive. Examples include:

  • blocks of logged-in users with a substantial history of valid contributions, regardless of the reason for the block
  • blocks that, while possibly wise, lack policy basis.
  • short term or cool-down blocks.

Once you are convinced that a block is warranted, the recommended procedure for controversial blocks is:

  1. Check the facts with care.
  2. Reread appropriate parts of Misplaced Pages:Blocking policy.
  3. If possible, contact other administrators to sanity-check your reasoning, preferably on ANI.
  4. Place the block, wording the "reason" message with care and without jargon, and include a link to the user page of the user being blocked.
  5. Place a notice of the block on the talk page of the affected user, with additional rationale, outlining the facts and the part of the blocking policy you feel applies.
  6. Stay around to discuss the block with other Wikipedians.
  7. If an act or acts of disruption do not warrant a 24-hour block, consider a warning or posting to ANI before issuing a short term block. (Someone may well block them longer than you would have!)

Block wars, in which a user is repeatedly blocked and unblocked, are extremely harmful. They frustrate and disappoint seasoned Wikipedians and encourage further bad behavior from the blocked user. If you disagree with a block, discuss the matter with the blocking admin and others, and try to reach a consensus, rather than unblocking — the blocking admin is likely to know more about the background of the situation than you do.

See also

Categories:
Misplaced Pages:Blocking policy: Difference between revisions Add topic