User:TomTheHand/block

Blocking is how administrators prevent a user account or IP address/range from editing Wikipedia. Blocks are used to prevent damage or disruption to Wikipedia and should not be used as a punitive measure. Block duration varies by situation, and a block may be lifted if the editor agrees to stop the damaging behavior.

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.

If you disagree with a block, start by discussing it with the blocking admin. (See Appealing a block.) Admins should not undo other admins' blocks without prior discussion, except in limited circumstances. (See If you disagree with a block.)

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

Purpose of blocking
The primary purpose of creating any block is to protect Wikipedia 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 WP:ANI 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. Examples include (but are not limited to):
 * Personal attacks which place users in danger (See No personal attacks)
 * Persistent personal attacks
 * Posting personal details
 * Persistent copyright infringement

Personal attacks that place users in danger
Blocks may be imposed where threats have been made or actions performed (including actions outside the Wikipedia site) that expose Wikipedia 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 Arbitration Committee (mailto:arbcom-l@wikipedia.org) and Jimbo Wales (mailto:jwales@wikia.com) about the block, and possibly contact someone with Oversight removal authority.

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 CheckUser policy.

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 npa6 template can be used. Users who make severe threats can be blocked indefinitely.

See No personal attacks and No legal threats for more information.

Disruption
A user may be blocked when his/her conduct severely disrupts the project &mdash; his/her 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 Wikipedia 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 Wikipedia.

Sysops may block IP addresses or usernames that disrupt the normal functioning of Wikipedia, or pose a sufficiently severe threat to it. Examples include (but are not limited to):
 * Vandalism
 * Excessive reverts (edit warring)
 * Violation of the three-revert rule
 * Inappropriate usernames (such blocks should not use the Account Creation Disabled blocking feature)
 * Abusive sockpuppet accounts
 * "Public" accounts, where the password is publicly available or shared with a large group
 * Anonymous and open proxies
 * Bots must have prior approval on Bots/Requests for approval and may be blocked if an admin thinks they are malfunctioning in a damaging way

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 Disruptive editing.

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.

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 WP:BLP, 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: blp1, blp2, and blp3. See the section on disruption above.

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

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 WP:ANI 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 Wikipedia:List of banned users (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
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.

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.)

Effects of being blocked
Blocked users and IP addresses can still see all Wikipedia 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, 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 &mdash; 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.

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 &mdash; 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. Also consider filing a Request for comment on use of admin privileges.

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.

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

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 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 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; however, they do affect autoblocks caused through that block.

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 Wikipedia 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.

Dynamic IP addresses
Most people edit Wikipedia from a dynamic IP address. This means that the IP address of their computer can change on a time frame ranging from every few months to every single time they connect to the Internet. Administrators should use caution applying long blocks to dynamic IP addresses, because the IP address could get assigned to a different person at any time. At that point, an innocent user will be unable to edit Wikipedia, and the person who was blocked will be able to edit from their new address.

A block for disruption on a dynamic IP should generally not exceed 24 hours. However, a dynamic IP address with a history of disruption may merit a longer block, if the disruption appears connected. For example, if a 24 hour block expires on an IP, and disruption of the same type resumes shortly afterward, escalating blocks should be used. However, if a dynamic IP was used for disruption several months ago and is disrupting Wikipedia again, but the disruption does not appear related, the old disruption should not be used as justification for an extended block.

Shared IP addresses
Shared IP addresses are addresses used by multiple users simultaneously. For example, school libraries often have many computers sharing the same IP address through a router, and students generally use computers for a short period of time. Some ISPs route their traffic through proxy servers, so hundreds of different users could be using the same IP address.

It is necessary to be even more cautious when blocking a shared IP address than when blocking a dynamic one. Blocks should generally be for short time periods (three hours or less), and should often be "soft" blocks. Again, a history of disruption may merit a longer block, but it is even more important to ensure that the disruption is connected.

Static IP addresses and logged-in users
Because there is little risk of blocking innocent users, less caution is necessary when blocking static IP addresses and logged-in users. However, care should be taken to avoid biting the newcomers. Blatant and harmful vandalism should be blocked swiftly, but mild unproductive edits should be warned first.

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.

Some types of disruption have more established guidelines:
 * 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 collateral damage. User accounts with persistent violations may be blocked indefinitely.
 * Personal attacks &mdash; 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.
 * 3RR violations &mdash; 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 &mdash; 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  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 sockpuppets &mdash; New accounts may be blocked for any length of time or permanently; sockpuppets 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; Bots are supposed to be blocked at sight if they do anything they're not cleared for at WP:BOT, 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 &mdash; This includes publishing personal details. Blocks are generally indefinite. 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 Oversight.

Indefinite blocks
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.

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.

Shared IPs
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 WHOIS and Reverse DNS lookup query on the IP to determine if it belongs to a school or a proxy server. If a Shared IP's talk page is not already identified or tagged as such, use either the or  templates to do so. For anonymous-only blocks of Shared IPs, please consider using or  as your blocking reason.

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.

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) 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 sysop privileges.

If an administrator disagrees with a block
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 a discussion on WP:AN/I 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.

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 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, e.g. if a user is angry about something controversial, blocking that user will rarely cool him or her down

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 Wikipedia:Blocking policy.
 * 3) Contact other administrators to sanity-check your reasoning, preferably on ANI.
 * 4) After receiving feedback, place the block, wording the "reason" message with care and without jargon.
 * 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!)
 * 8) If in doubt, don't block.

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 &mdash; the blocking admin is likely to know more about the background of the situation than you do.