| Revision as of 14:11, 28 April 2007 view sourceTony Sidaway (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers81,722 edits Remove piped WP:WARN shortcut and replace by target← Previous edit | Revision as of 16:32, 28 April 2007 view source Stephen Bain (talk | contribs)Extended confirmed users12,147 edits rewriteNext edit → | ||
| Line 2: | Line 2: | ||
| {{policy in a nutshell|Users may be blocked from editing by an administrator to protect Misplaced Pages and its editors from harm.|align=center}} | {{policy in a nutshell|Users may be blocked from editing by an administrator to protect Misplaced Pages and its editors from harm.|align=center}} | ||
| '''Blocking''' is |
'''Blocking''' is the method by which ] may prevent users (whether registered accounts, IP addresses or IP ranges) from editing ]. Blocks are used in order to prevent damage or disruption to Misplaced Pages, not to punish users. | ||
| Any user may request a block at the ] or a specialised venue such as the ]. Users requesting blocks should supply credible evidence of the circumstances warranting a block. Administrators are never obliged to place a block and are free to investigate the situation themselves. | |||
| If you wish to contest a block, see ] for further instructions. | |||
| A variety of ] exist to warn users of undesirable behavior that may lead to a block. Their purpose is in part to notify novice users they may be breaking a policy they are unfamiliar with. These templates exist solely as a convenience to editors who repeatedly make similar warnings. The templates do not form a mandatory part of blocking process, and to long-term users, custom-written warnings are more appropriate than the premade warnings. | |||
| ==When blocking may be used== | |||
| If you disagree with a block, start by discussing it with the blocking admin. (''See'' ].) Admins should not undo other admins' blocks without prior discussion, except in limited circumstances. (''See'' ]) | |||
| The following are the most common situations when blocking may be used. This is not an exhaustive list; blocking may be used in other situations, particularly situations addressed by more specific policies dealing with particular issues. | |||
| ''Note:'' When blocking an IP address, watch for ]. | |||
| Even though this is not an exhaustive list, if a situation is not listed below, then a block is more likely to be controversial than otherwise. A rule of thumb is when in doubt, do not block; instead, consult other administrators for advice. After placing a block that may be controversial, it is a good idea to make a note of the block at the ] for sanity checking. | |||
| ==Purpose of blocking== | |||
| The primary purpose of creating any block is to protect Misplaced Pages and its editors and users from harm. The following list includes the most common grounds, however note that the block reason not being on this list is not in itself a reason to unblock. If blocking for a reason not listed, be sure to note it on ] for sanity-checking. | |||
| ===Protection=== | ===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 which place users in danger (See ]) | |||
| * Persistent personal attacks | |||
| * Posting personal details | |||
| * Persistent copyright infringement | |||
| A user may be blocked when necessary to protect the rights, property or safety of the ], its users or the public. A block for protection may be necessary in response 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. The admin should email the ] () about the block, and possibly contact someone with ] removal authority to permanently remove the information from the page history. | |||
| * persistently making ] | |||
| 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 or not the personal details are accurate. Nothing in this provision should be taken to apply to users with CheckUser access making information available within the terms of the ]. | |||
| * making personal, professional or ] threats | |||
| * performing actions or making threats (including outside the Misplaced Pages site) that place users in danger | |||
| * disclosing personal information (whether or not the information is accurate) | |||
| * persistently ] | |||
| When blocking in response to disclosing personal information or actions that place users in danger, consider notifying the ] () about the block and contacting someone with ] to hide the material in question. | |||
| The Arbitration Committee has not reached a conclusive and binding decision pertaining to the addition of links to or material derived from sites that engage in attacks and harassment against Misplaced Pages users, as documented by two different cases ] and ]. | |||
| ===Disruption=== | |||
| ====Making personal or legal threats against other users==== | |||
| Users who make threats, whether legal, personal, or professional, that in any way are seen as an attempt to intimidate another user may be blocked without warning. If a warning is desirable, the {{tl|npa6}} template can be used. Users who make severe threats can be blocked indefinitely. | |||
| A user may be blocked when his or her conduct severely disrupts the project; that is, when his or her conduct is inconsistent with a ] and interferes with the process of editors working together harmoniously to create an encyclopedia. A block for disruption may be necessary in response to: | |||
| See ] and ] for more information. | |||
| * persistent ] | |||
| ===Disruption=== | |||
| * persistent ] | |||
| A user may be blocked when his/her conduct severely disrupts the project — his/her conduct is inconsistent with a civil, collegial atmosphere and interferes with the process of editors working together harmoniously to create an encyclopedia. | |||
| * persistent ] | |||
| * persistently posting unsourced or poorly sourced contentious ] | |||
| * persistent ] | |||
| * ] | |||
| * breaching the ] | |||
| * breaching the ] | |||
| Blocks for disruptive behaviour should not typically be used in response to isolated instances of behaviour, but in response to persistent patterns of behaviour. | |||
| 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. | |||
| Furthermore, some types of user accounts are considered disruptive and may be blocked: | |||
| Administrators 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): | |||
| * ] | |||
| * Excessive reverts (]) | |||
| * Violation of the ] | |||
| * ] (such blocks should '''not''' use the ''Account Creation Disabled'' blocking feature unless they are obviously disruptive, i.e., "EDITOR X IS UGLY") | |||
| * Abusive ] accounts | |||
| * "Public" accounts, where the password is publicly available or shared with a large group | |||
| * ] | |||
| * ] must have prior approval on ] and may be blocked if an admin thinks they are malfunctioning in a damaging way | |||
| * public accounts (where the password is publicly available or shared with a large group) | |||
| Blocks for general incivility are controversial; "cool-down" blocks are ''very'' controversial. Consider whether a 1-hour block will result in 2 months' drama. ''See'' ]. | |||
| * accounts with ] | |||
| * ] operating without ] or outside their approval | |||
| ===Enforcing bans=== | |||
| 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. | |||
| {{details|Misplaced Pages:Banning policy}} | |||
| ====Biographies of living persons==== | |||
| {{see|Misplaced Pages:Biographies of living persons}} | |||
| Editors who repeatedly insert unsourced or poorly sourced contentious biographical material about living persons to articles or talk pages may be blocked for disruption. 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. | |||
| A Misplaced Pages ban is a formal revocation of editing privileges on all or part of Misplaced Pages. A ban may be temporary and of fixed duration, or indefinite and potentially permanent. | |||
| ====Advertising==== | |||
| Accounts that appear, based on their edit history, to exist for the '''sole or primary purpose''' of promoting a person, company, product, or service, in apparent violation of ], shall be warned that such edits are against Misplaced Pages policy. If after the warning such edits persist, and the account continues to be used primarily or solely for the purpose of promotion, any uninvolved admin may block the account for up to one week. If such edits persist after the block, the account may be blocked indefinitely. A legitimate content dispute shall not be considered as a reason for such blocks. | |||
| Blocks may be used to enforce bans. Such blocks are based on the particular terms of the ban. Except for partial bans, banned users are customarily blocked for the duration of the ban. | |||
| ===Bans=== | |||
| {{main|Misplaced Pages:Banning policy}} | |||
| ====Open or anonymous proxies==== | |||
| Banned users are typically blocked from editing all or parts of Misplaced Pages. They may be banned by the ], by ] or by the ] ]. | |||
| {{details|Misplaced Pages:No open proxies}} | |||
| There have been situations where a user has exhausted the community's patience to the point where he or she finds themselves banned. 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. Additionally, '''"community ban"''' wording should be noted in the block log. 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. | |||
| A special instance of using blocks to enforce bans relates to ]. The use of open or anonymous proxies is banned on all Wikimedia projects by the ]. | |||
| ===Self-requested blocks=== | |||
| Sometimes people request that their account be blocked, generally to enforce a ]. In general, such requests are refused because such blockings can lead to corollary damage through other uninvolved editors on the same IP becoming blocked. There exists a ] that can be used instead. | |||
| Such proxies may be blocked indefinitely. Non-static IPs or hosts that are otherwise not permanent proxies typically warrant blocking for a shorter period of time, as the IP is likely to be transferred, the open proxy is likely to be closed, or the IP is likely to be re-assigned dynamically. | |||
| There is also a Misplaced Pages project, the ], which seeks to identify and block open proxy servers. | |||
| ===Evasion of blocks=== | ===Evasion of blocks=== | ||
| A blocked user cannot edit any pages other than his/her own talk page. An admin may restart the block of a user who intentionally evades a block, and may extend the original block if the user commits further blockable acts. Accounts and IPs used in evading a block may also be blocked. | |||
| An administrator may reset the block of a user who intentionally evades a block, and may extend the duration of the block if the user engages in further blockable behaviour while evading the block. User accounts or IP addresses used to evade a block may also be blocked. | |||
| Edits made by blocked users while blocked ''may'' be reverted. (Admins can revert all edits from blocked users and re-make the good edits under their own names, to avoid confusing other admins who may be monitoring the same users.) | |||
| ==When blocking may not be used== | |||
| ==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 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. | |||
| ===Disputes=== | |||
| When a blocked user attempts to edit, his/her 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, his/her IP will be automatically unblocked 24 hours after he or she last attempted to edit a page. This option can be disabled for individual blocks. | |||
| Administrators must not block users with whom they are engaged in a content dispute or personal dispute. Instead, they should report the problem to other administrators. | |||
| 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 an administrator. | |||
| == |
===Cool-down blocks=== | ||
| 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 an IP change can be forced. If that is not possible, the block should be reported to the blocking admin and/or the nearest friendly admin via email — see the ] for some likely candidates. IRC #wikipedia may also be useful. | |||
| Cool down blocks - brief blocks solely for the purpose of "cooling down" an angry user - should not be used, as they inevitably serve to inflame the situation. | |||
| 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.) | |||
| ===Self-requested blocks=== | |||
| 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. Edit so as to demonstrate your trustworthiness, not to put up a façade of untrustworthiness. | |||
| Sometimes people request that their account be blocked, for example to enforce a ]. Typically such requests are refused, because of the possibility of collateral effects to other users using the same IP address. There is a Javascript-based "]" which may be used instead. | |||
| ==When blocking may not be used== | |||
| Blocking to gain an advantage in a content dispute is strictly prohibited. Admins 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. Also consider filing a ]. | |||
| ===Recording in the block log=== | |||
| Very brief blocks, for instance of one second, are sometimes used for the purpose of recording warnings or other negative events in a user's block log. This practice can be seen as humiliating, and is not approved, except for making notes that are in the user's own interest. For instance, when a wrongful block has originally been placed, a one-second block can later be added by the same admin in order to record an apology, or acknowledgement of mistake. | |||
| Blocks should not be used solely for the purpose of recording warnings or other negative events in a user's block log. The practice, typically involving very short blocks (eg, of one second duration), is often seen as punitive and humiliating. | |||
| Caution should be exercised before blocking users who may be acting in good faith. | |||
| However, very brief blocks may be used in order to record, for example, an apology or acknowledgment of mistake in the block log in the event of a wrongful or accidental block, unless the original block has not yet expired (in which case the message may be recorded in the unblocking reason). | |||
| ==Instructions to admins== | |||
| ===How to block=== | |||
| 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 ] (]). | |||
| ==Unblocking== | |||
| 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. | |||
| Administrators should not unblock users blocked by other administrators without first attempting to contact the blocking administrator and discuss the matter with them. It may not necessarily be obvious what the problem necessitating blocking was, and it is a matter of courtesy and common sense to consult the blocking administrator. If the blocking administrator is not available, or if the administrators cannot come to an agreement, then a discussion at the ] is recommended. | |||
| ====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; however, they do affect autoblocks caused through that block. | |||
| If a block is the result of an unambiguous error, and not a judgment call (for example, if the blocking administrator obviously misspelt a username), and the blocking administrator is not available, then it is not necessary to discuss prior to unblocking. Where there is ambiguity, then approach the block as normal. When in doubt, do not unblock. ] is considered very harmful. | |||
| 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". | |||
| === |
===Altering block options=== | ||
| 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 an admin explicitly unblocks the account. | |||
| Administrators may unblock a user in order to re-block that user with different blocking options selected, where that is necessary (for example, if a block on a registered account is causing significant collateral effects to a shared IP address). | |||
| If no expiry time is entered, an error message will be displayed. | |||
| ===Temporary circumstances blocks=== | |||
| 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. | |||
| Some types of blocks are used in response to particular temporary circumstances, and should be undone once the circumstance no longer applies: | |||
| A block for disruption on a dynamic IP is usually 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 on IPs; many IPs are dynamically assigned and change frequently from one person to the next, and sometimes even static IP addresses can be re-assigned or have different users. Longer IP blocks on the order of months or years can be warranted in cases of long-term recurrent disruption, but are not to be used for isolated incidents of disruption from IP addresses, nor at first against user accounts that make a mixture of disruptive and useful edits. | |||
| * blocks on ] should be undone once it is confirmed that they have been "closed"; | |||
| Some types of disruption have more established guidelines: | |||
| * blocks of unapproved or malfunctioning bots should be undone once the bots gain approval or are repaired; | |||
| * '''Vandalism: ]''' (]) | |||
| * blocks for making ] should be undone once the threats are no longer outstanding. | |||
| *:Blocks should generally not be used against isolated incidents of vandalism. Dynamic IPs: up to 31 hours. Range blocks: about 15 minutes, then 1-3 hours, and 31 at most, to avoid ]. User accounts with persistent violations may be blocked indefinitely. | |||
| * '''Personal attacks: ] (])''' | |||
| *: Blocks should not normally be used against general incivility or isolated incidents of personal attacks. Again, 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. User accounts with persistent violations may be blocked indefinitely. | |||
| * '''Three revert rule: ] (])''' | |||
| *: Generally 24 hours in the first instance; longer for repeated or aggravated violations. A notice of the block should be left on the user's talk page. | |||
| * '''Inappropriate usernames: ] (])''' | |||
| *: If malicious (e.g. impersonation of another user), indefinitely blocked at sight; IP address should be left autoblocked. If not (e.g. name of a celebrity), consider warning a user before blocking and remember to include {{Template|UsernameBlock}} in the "reason" field with a link to any discussion. '''If the username is not malicious, please uncheck the " Automatically block the last IP address used by this user, and any subsequent addresses they try to edit from" checkbox on the Block page''' | |||
| * '''Abusive sock puppets ] (])''' | |||
| *:New accounts may be blocked for any length of time or permanently; ] 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''' | |||
| *: Bots are supposed to be blocked at sight if they do anything they're not cleared under the ] (]), or if broken somehow. 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. Remember to disable autoblock, as otherwise you may also block the bot's operator too. | |||
| * '''Personal attacks which place users in danger''' | |||
| *: This includes publishing personal details. Blocks are generally indefinite. Admins applying such sanctions should confidentially notify the members of the ] (arbcom-l@wikipedia.org) and Jimbo Wales (jwales@wikia.com) of what they have done and why. See also ]. | |||
| == |
==Implementing blocks== | ||
| Technical instructions on how to block and unblock, and information on the blocking interface, is available at ]. The following is advice specifically related to blocking and unblocking on Misplaced Pages. | |||
| An indefinite block is one where the blocks length of term has been set to 'infinite' or 'indefinite' by the admin placing the block. Indefinite blocks are used to prevent a specific account from editing. This may be because the account itself is not to be used for various reasons, or because the individual who created it is banned or using it as an abusive single purpose account. | |||
| In addition to the advice below, there are special considerations to take into account when blocking IP addresses. See ] and ]. | |||
| Inappropriate usernames, policy-breaching sockpuppets, and single-purpose abusive accounts that have not made significant constructive edits can be indefinitely blocked on sight, and should be noted in the block summary. This includes accounts used predominantly for vandalism, personal attack, or threats. Established users with significant constructive edits should not be indefinitely blocked except when there is a community ban. In all other cases, they should be handled with appropriate time-limited blocks or arbitration. Indefinite blocks should not usually be placed on IP users (whether individual IPs or IP ranges) in order to avoid inadvertently blocking legitimate users. | |||
| === |
===Education and warnings=== | ||
| Before implementing a long-term block on an IP address with a long history of vandalism, please check if it is shared by performing a ] and ] query on the IP to determine if it belongs to a school or a ]. If a Shared IP's talk page is not already identified or tagged as such, use either the <tt>{{]}}</tt> or <tt>{{]}}</tt> templates to do so. ] IPs such as those with the substring "dhcp", "dyn" or "pool" in their ]s can be tagged using <tt>{{]}}</tt> template. | |||
| Everyone was new once, and most of us made mistakes when new. That's why we ] and are ], and ] that most people who work on the project are trying to help it, not hurt it. We also ask that newcomers make an effort to learn about ] so that they can learn how to avoid making mistakes. | |||
| When applying anonymous-only blocks of Shared IPs, please consider using <tt>{{]}}</tt> or <tt>{{]}}</tt> as your blocking reason. | |||
| <!-- | |||
| To determine if a ] is operating from an IP address, a ] such as ] can also be used. For example, | |||
| :<code>$ nmap -A -p80,3128,8080 <''ip address''></code> | |||
| will perform a quick scan to identify such servers on the common HTTP proxy ports of 80, 3128 and 8080. | |||
| --> | |||
| As such, before blocking is used, efforts should be made to educate users about our policies and guidelines, and to warn them when their behaviour is in conflict with our policies and guidelines. A ] exist for convenience, although purpose-written messages are often preferable. | |||
| ===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 judgment and make them as brief as possible. When making a range block, an administrator should note the range in the block reason. If you do not do so, and a block is appealed, it is impossible to tell what the blocked IP is. | |||
| Warning is not a prerequisite for blocking (particularly with respect to blocks for protection) but administrators should generally ensure that users are aware of policies, and give them reasonable opportunity to adjust their behaviour accordingly, before blocking. Users who have been made aware of a policy and have had such an opportunity do not require further warning. | |||
| 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 on the ] . See ]. | |||
| === |
===Duration of blocks=== | ||
| ] contains a list of all currently blocked users and IPs. Admins will see a link to (<span class="plainlinks"><font color=blue></font></span>) 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. | |||
| The purpose of blocking is prevention, not punishment. The duration of blocks should thus be related to the likelihood of a user repeating inappropriate behaviour. Administrators should consider: | |||
| Admins 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) with which they share an IP. 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 a convincingly good reason has resulted in several users losing their admin privileges. | |||
| * the severity of the behaviour; | |||
| === If an administrator disagrees with a block === | |||
| * whether the user has been blocked for engaging in that behaviour before. | |||
| If you are an administrator and disagree with a block placed by another administrator, do not unblock without first attempting to contact the blocking admin and discussing the matter. If the blocking admin is unavailable for comment, or you cannot come to an agreement with the blocking admin, a discussion on ] (]) or ] (]) is recommended. Blocked users sometimes e-mail several admins claiming to be the victims of an unjust block, 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. | |||
| Blocks on shared or dynamic IP addresses are typically shorter than blocks on registered accounts or static IP addresses made in otherwise similar circumstances, in order to limit side effects on other users sharing that IP address. | |||
| Exceptions to this include situations where an unambiguous error has been made (not a judgment call) and the blocking admin is not online. If the blocking admin is not available, you should notify the blocking admin on his or her talk page and possibly a note to ] (]).. | |||
| While the duration of a block should vary with the circumstances of the block, there are some broad standards for block durations: | |||
| ===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, e.g. if a user is angry about something controversial, blocking that user will rarely cool him or her down | |||
| * blocks for all types of disruptive behaviour are typically for 24 hours, longer for successive instances; | |||
| Once you are convinced that a block is warranted, the recommended procedure for controversial blocks is: | |||
| * blocks on types of user accounts considered disruptive are typically of indefinite duration; | |||
| * blocks for protection are typically for as long as protection is necessary, which may often be indefinitely. | |||
| ===Setting block options=== | |||
| # Check the facts with care. | |||
| # Reread appropriate parts of Misplaced Pages:Blocking policy. | |||
| # Contact other administrators to sanity-check your reasoning, preferably on ] (]). | |||
| # After receiving feedback, place the block, wording the "reason" message with care and without jargon. | |||
| # 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. | |||
| # 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!) | |||
| # If in doubt, don't block. | |||
| {{details | Help:Block and unblock#Blocking options }} | |||
| ], 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. | |||
| There are several options available to modify the effect of blocks, which should be used in certain circumstances. | |||
| * '''autoblock''' should typically be ''disabled'' when blocking unapproved or malfunctioning bots (so as not to block the bot's operator), though it should be ''enabled'' when blocking malicious bots | |||
| * '''prevent account creation''' should typically be ''disabled'' when blocking accounts with inappropriate usernames (so as to allow the user to create an account with an appropriate name), though it should be ''enabled'' when blocking malicious usernames (eg, clear impersonations of other users) | |||
| A "softblock" is a block with autoblock disabled, account creation disabled, and blocking only anonymous users enabled. The effect is to block anonymous users but allow registered users to continue editing. Softblocks are commonly used when blocking shared IP addresses. | |||
| ===Reasons and notification=== | |||
| Administrators should take care to supply a clear and specific block reason which indicates why a user was blocked. Block reasons should avoid the use of jargon as much as possible so that blocked users may better understand them. Administrators should also notify users when blocking them by leaving a message on their user talk page. It is much easier to explain a block well when making it than it is to explain a block well after the fact. | |||
| There are a number of template messages for blocking reasons and block notification which may be used for convenience; see ] and ]. | |||
| ==See also== | ==See also== | ||
| * ] | |||
| * ] & ] - information relating to blocking IP addresses | |||
| * ], text shown to blocked users | |||
| * ] |
* ] - information about contesting a block | ||
| * ] | |||
| * ] mailing list | |||
| * ] - the message shown to blocked users when they attempt to edit | |||
| * ], category containing user block templates | |||
| * ] | |||
| * ], an arbitration case after which several admins were stripped of administratorship due to the titular ]. | |||
| ] | ] | ||
Revision as of 16:32, 28 April 2007
 | 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: Users may be blocked from editing by an administrator to protect Misplaced Pages and its editors from harm. |
Blocking is the method by which administrators may prevent users (whether registered accounts, IP addresses or IP ranges) from editing Misplaced Pages. Blocks are used in order to prevent damage or disruption to Misplaced Pages, not to punish users.
Any user may request a block at the administrators' noticeboard for incidents or a specialised venue such as the administrator intervention against vandalism noticeboard. Users requesting blocks should supply credible evidence of the circumstances warranting a block. Administrators are never obliged to place a block and are free to investigate the situation themselves.
If you wish to contest a block, see Misplaced Pages:Appealing a block for further instructions.
When blocking may be used
The following are the most common situations when blocking may be used. This is not an exhaustive list; blocking may be used in other situations, particularly situations addressed by more specific policies dealing with particular issues.
Even though this is not an exhaustive list, if a situation is not listed below, then a block is more likely to be controversial than otherwise. A rule of thumb is when in doubt, do not block; instead, consult other administrators for advice. After placing a block that may be controversial, it is a good idea to make a note of the block at the administrators' noticeboard for sanity checking.
Protection
A user may be blocked when necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public. A block for protection may be necessary in response to:
- persistently making personal attacks
- making personal, professional or legal threats
- performing actions or making threats (including outside the Misplaced Pages site) that place users in danger
- disclosing personal information (whether or not the information is accurate)
- persistently violating copyright
When blocking in response to disclosing personal information or actions that place users in danger, consider notifying the Arbitration Committee (by email) about the block and contacting someone with oversight permissions to hide the material in question.
Disruption
A user may be blocked when his or her conduct severely disrupts the project; that is, when his or her conduct is inconsistent with a civil, collegial atmosphere and interferes with the process of editors working together harmoniously to create an encyclopedia. A block for disruption may be necessary in response to:
- persistent vandalism
- persistent gross incivility
- persistent harassment
- persistently posting unsourced or poorly sourced contentious biographical material about living persons
- persistent spamming
- edit warring
- breaching the three revert rule
- breaching the sock puppetry policy
Blocks for disruptive behaviour should not typically be used in response to isolated instances of behaviour, but in response to persistent patterns of behaviour.
Furthermore, some types of user accounts are considered disruptive and may be blocked:
- public accounts (where the password is publicly available or shared with a large group)
- accounts with inappropriate usernames
- bots operating without approval or outside their approval
Enforcing bans
Further information: Misplaced Pages:Banning policyA Misplaced Pages ban is a formal revocation of editing privileges on all or part of Misplaced Pages. A ban may be temporary and of fixed duration, or indefinite and potentially permanent.
Blocks may be used to enforce bans. Such blocks are based on the particular terms of the ban. Except for partial bans, banned users are customarily blocked for the duration of the ban.
Open or anonymous proxies
Further information: Misplaced Pages:No open proxiesA special instance of using blocks to enforce bans relates to open or anonymous proxies. The use of open or anonymous proxies is banned on all Wikimedia projects by the Wikimedia Foundation.
Such proxies may be blocked indefinitely. Non-static IPs or hosts that are otherwise not permanent proxies typically warrant blocking for a shorter period of time, as the IP is likely to be transferred, the open proxy is likely to be closed, or the IP is likely to be re-assigned dynamically.
There is also a Misplaced Pages project, the WikiProject on open proxies, which seeks to identify and block open proxy servers.
Evasion of blocks
An administrator may reset the block of a user who intentionally evades a block, and may extend the duration of the block if the user engages in further blockable behaviour while evading the block. User accounts or IP addresses used to evade a block may also be blocked.
When blocking may not be used
Disputes
Administrators must not block users with whom they are engaged in a content dispute or personal dispute. Instead, they should report the problem to other administrators.
Cool-down blocks
Cool down blocks - brief blocks solely for the purpose of "cooling down" an angry user - should not be used, as they inevitably serve to inflame the situation.
Self-requested blocks
Sometimes people request that their account be blocked, for example to enforce a wikibreak. Typically such requests are refused, because of the possibility of collateral effects to other users using the same IP address. There is a Javascript-based "wikibreak enforcer" which may be used instead.
Recording in the block log
Blocks should not be used solely for the purpose of recording warnings or other negative events in a user's block log. The practice, typically involving very short blocks (eg, of one second duration), is often seen as punitive and humiliating.
However, very brief blocks may be used in order to record, for example, an apology or acknowledgment of mistake in the block log in the event of a wrongful or accidental block, unless the original block has not yet expired (in which case the message may be recorded in the unblocking reason).
Unblocking
Administrators should not unblock users blocked by other administrators without first attempting to contact the blocking administrator and discuss the matter with them. It may not necessarily be obvious what the problem necessitating blocking was, and it is a matter of courtesy and common sense to consult the blocking administrator. If the blocking administrator is not available, or if the administrators cannot come to an agreement, then a discussion at the administrators' noticeboard is recommended.
If a block is the result of an unambiguous error, and not a judgment call (for example, if the blocking administrator obviously misspelt a username), and the blocking administrator is not available, then it is not necessary to discuss prior to unblocking. Where there is ambiguity, then approach the block as normal. When in doubt, do not unblock. Wheel warring is considered very harmful.
Altering block options
Administrators may unblock a user in order to re-block that user with different blocking options selected, where that is necessary (for example, if a block on a registered account is causing significant collateral effects to a shared IP address).
Temporary circumstances blocks
Some types of blocks are used in response to particular temporary circumstances, and should be undone once the circumstance no longer applies:
- blocks on open or anonymous proxies should be undone once it is confirmed that they have been "closed";
- blocks of unapproved or malfunctioning bots should be undone once the bots gain approval or are repaired;
- blocks for making legal threats should be undone once the threats are no longer outstanding.
Implementing blocks
Technical instructions on how to block and unblock, and information on the blocking interface, is available at Help:Block and unblock. The following is advice specifically related to blocking and unblocking on Misplaced Pages.
In addition to the advice below, there are special considerations to take into account when blocking IP addresses. See Misplaced Pages:Blocking IP addresses and Misplaced Pages:Sensitive IP addresses.
Education and warnings
Everyone was new once, and most of us made mistakes when new. That's why we welcome newcomers and are patient with them, and assume that most people who work on the project are trying to help it, not hurt it. We also ask that newcomers make an effort to learn about our policies and guidelines so that they can learn how to avoid making mistakes.
As such, before blocking is used, efforts should be made to educate users about our policies and guidelines, and to warn them when their behaviour is in conflict with our policies and guidelines. A variety of template messages exist for convenience, although purpose-written messages are often preferable.
Warning is not a prerequisite for blocking (particularly with respect to blocks for protection) but administrators should generally ensure that users are aware of policies, and give them reasonable opportunity to adjust their behaviour accordingly, before blocking. Users who have been made aware of a policy and have had such an opportunity do not require further warning.
Duration of blocks
The purpose of blocking is prevention, not punishment. The duration of blocks should thus be related to the likelihood of a user repeating inappropriate behaviour. Administrators should consider:
- the severity of the behaviour;
- whether the user has been blocked for engaging in that behaviour before.
Blocks on shared or dynamic IP addresses are typically shorter than blocks on registered accounts or static IP addresses made in otherwise similar circumstances, in order to limit side effects on other users sharing that IP address.
While the duration of a block should vary with the circumstances of the block, there are some broad standards for block durations:
- blocks for all types of disruptive behaviour are typically for 24 hours, longer for successive instances;
- blocks on types of user accounts considered disruptive are typically of indefinite duration;
- blocks for protection are typically for as long as protection is necessary, which may often be indefinitely.
Setting block options
Further information: Help:Block and unblock § Blocking optionsThere are several options available to modify the effect of blocks, which should be used in certain circumstances.
- autoblock should typically be disabled when blocking unapproved or malfunctioning bots (so as not to block the bot's operator), though it should be enabled when blocking malicious bots
- prevent account creation should typically be disabled when blocking accounts with inappropriate usernames (so as to allow the user to create an account with an appropriate name), though it should be enabled when blocking malicious usernames (eg, clear impersonations of other users)
A "softblock" is a block with autoblock disabled, account creation disabled, and blocking only anonymous users enabled. The effect is to block anonymous users but allow registered users to continue editing. Softblocks are commonly used when blocking shared IP addresses.
Reasons and notification
Administrators should take care to supply a clear and specific block reason which indicates why a user was blocked. Block reasons should avoid the use of jargon as much as possible so that blocked users may better understand them. Administrators should also notify users when blocking them by leaving a message on their user talk page. It is much easier to explain a block well when making it than it is to explain a block well after the fact.
There are a number of template messages for blocking reasons and block notification which may be used for convenience; see Category:User block templates and Misplaced Pages:Template messages/User talk namespace.
See also
- Misplaced Pages:Blocking IP addresses & Misplaced Pages:Sensitive IP addresses - information relating to blocking IP addresses
- Misplaced Pages:Appealing a block - information about contesting a block
- Misplaced Pages:Autoblock
- MediaWiki:Blockedtext - the message shown to blocked users when they attempt to edit
- Category:User block templates