Misplaced Pages

This is an old revision of this page, as edited by 88.107.78.52 (talk) at 19:34, 8 August 2006 (→Evasion of blocks). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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 ]

"WP:BP" redirects here. For the banning policy, see Misplaced Pages:Banning policy (WP:BAN).

An amendment to this policy is currently being discussed at Misplaced Pages:Blocking policy proposal.

Blocking is the means by which a Misplaced Pages administrator prevents a user account or IP address/range from editing Misplaced Pages. Blocks are preventive rather than punitive measures used to prevent damage to Misplaced Pages by dealing with vandalism and enforcing bans 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.

All users may post block requests at Administrators' noticeboard/Incidents or other venues listed below, which may result in quick action where credible evidence of policy violations is provided.

If you disagree with a block, begin by discussing it with the blocking admin. See Appealing a block for more information. Admins are never obliged to place a block. Admins and bureaucrats may also be blocked, with resulting effects on their other privileges.

When blocks may be used

Vandalism

Report at Administrator intervention against vandalism

Sysops may block IP addresses whose users vandalise Misplaced Pages. There are various rules of thumb by which sysops decide how far to extend the blocks of habitual vandals, none of which is formal policy. In general, casual vandals will be warned before being blocked, though warnings are not usually given for deliberate vandalism intended to discredit Misplaced Pages or serve an activist agenda.

Excessive reverts

Report at Administrators' noticeboard - 3RR

Sysops may block users for edit warring. As a rule of thumb, this happens when an editor reverts for the fourth time in a 24-hour period (see WP:3RR). Where multiple parties violate the rule, sysops will treat all sides equally.

Personal attacks which place users in danger

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.

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 unsourced, or incorrectly sourced, and may constitute defamation. 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 below.

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 admins with CheckUser access, who may make certain information available within the terms of the CheckUser policy.

Disruption

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, harassment, excessive personal attacks, and inserting material that may be defamatory. Users will normally be warned before they are blocked.

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.

Note that disagreements over content 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.

Copyright infringement and plagiarism

Inserting other people's work into Misplaced Pages without permission or attribution is unacceptable. Copyright infringement and plagiarism 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.

Fair-use images on user pages are not allowed and may be removed where they are found, which can most often be achieved with a polite talk-page request. Repeated insertion of fair-use images on user pages may be grounds for blocking, subject to the provision above. Another option is to remove the image and protect the user page.

Jimbo has said the following:

We need to deal with such activities with absolute harshness, no mercy, because this kind of plagiarism is 100% at odds with all of our core principles. All admins are invited to block any and all similar users on sight. Be bold. If someone takes you to ArbCom over it, have no fear. We must not tolerate plagiarism in the least. Jimbo Wales 04:28, 28 December 2005 UTC)

There is no need nor intention to be vindictive, but at the same time, we can not tolerate plagiarism. Let me say quite firmly that for me, the legal issues are important, but far far far more important are the moral issues. We want to be able, all of us, to point at Misplaced Pages and say: we made it ourselves, fair and square. Jimbo Wales 15:54, 28 December 2005 (UTC)

I support serious action to ban people who commit copyvios. We are supposed to be using fair use only in certain very limited circumstances and people who do not realize that should be banned from the project. Jimbo Wales May 19 23:33:12 UTC 2006

Usernames

According to our username policy, 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.

Bans

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 Arbitration Committee, ruling by Jimbo Wales, or ruling by the Wikimedia Board of Trustees.

When it becomes clear that a user account is a "reincarnation" of an existing banned user, the new account should likewise be blocked. See Misplaced Pages:Sock puppet for discussion.

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 WP:ANI as part of the review process. With such support, the user is considered banned and must be listed on Misplaced Pages: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.

"Public" accounts

Misplaced Pages convention is that accounts with a specific name, but created for use by multiple people, are not to be used. These are seen as pretending to a reputation as an individual within the Misplaced Pages project, while masking anonymity. So-called "public" accounts are not considered necessary because anonymous users can edit freely, and anyone can quickly create a username without even an email address being required. Examples include any account where the owner posts the password for public use. These may be blocked on sight indefinitely.

Bots

Bots must have prior approval on Misplaced Pages talk:Bots, 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

Administrators are permitted and encouraged to IP-block anonymous proxies indefinitely . See the entire thread for discussions about the legitimacy of using an anonymous proxy to edit Misplaced Pages. Such blocks are routine though some consider them a bad idea: .

User:Proxy blocker was once used to automatically block open proxies, but was turned off as it "spooked" some people's ISPs.

The suggested block message is {{blocked proxy}}.

Death

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

Evasion of blocks

ieughyucgnhgenhubgyunegfnugnegjiegnenhiegnhiceghcgchwnxgxhmnmhehxsgnhgnheg

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

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.

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—see the list of administrators for some likely candidates.

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.

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.

Generally, caution should be exercised before blocking users who may be acting in good faith.

Self-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

Sysops may go to Special pages and select the "Block a user/IP address" link. This takes them to Special:Blockip, which has further instructions. 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.

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

There are two options available at Special:Blockip 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.

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.

Expiry times and application

Expiry times are entered in the GNU standard format, which is described in the tar manual. 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.

• Vandalism — 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 collateral damage 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 — 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. Sysops blocked under this provision must not unblock themselves.
• Disruption — 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 Sockpuppets 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 — 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 Template:UsernameBlock in the block message (by writing {{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 RfC page on the blocked user's userpage. It is not advisable to create user pages or talk pages for users with offensive usernames. Care should be taken to unblock the user's IP address. To unblock the IP but not the username, wait until the user next tries to edit a page, and something like #1234 was blocked because they share an IP with OldUserName will appear at Special:Ipblocklist. Click "unblock" next to that number. Then the user can log in under their new name. If an account has been blocked both for vandalism and for having an inappropriate username, the IP should be left auto-blocked. Accounts and IP addresses that illegitimately use another account's name in the signature should be warned first, and then can be blocked.
• Public accounts — 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 Special:Preferences and change the password. This makes the password no longer public, and can also be done by anyone, not just an administrator.
• Bots — 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 — Sysops applying such sanctions should confidentially notify the members of the Arbitration Committee and Jimbo Wales of what they have done and why.

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.

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

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 WP:AN/I 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.

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

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 disruption provision of the blocking policy.
• blocks that, while possibly wise, lack policy basis.

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 informally to be sure there are others who agree with your reasoning. The administrators' noticeboard, IRC and email are effective tools for this.
4. 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.
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. Be willing to discuss the block with other Wikipedians.

Block wars, 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.

See also

• MediaWiki:Blockedtext, text shown to blocked users
• Misplaced Pages:Appealing a block, page where blocked users who wish to appeal are directed
• unblock-en-l mailing list
• Misplaced Pages:Semi-block, a proposed amendment to the blocking policy.
• Category:User block templates, category containing user block templates
• Blacklist

• Misplaced Pages policies
• Misplaced Pages user intervention