Misplaced Pages

:Blocking policy: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 23:05, 20 January 2006 view sourceRexNL (talk | contribs)Extended confirmed users62,499 editsm Reverted edits by 24.222.38.8 (talk) to last version by FeloniousMonk← Previous edit Revision as of 13:10, 21 January 2006 view source Aaron Brenneman (talk | contribs)Extended confirmed users19,683 edits moving things around quite a lot to remove repition. anything actually _removed_ noted on talk.Next edit →
Line 1: Line 1:
{{policy2|]}} {{policy2|]}}


'''Blocking''' is one of the technical means by which bans are enforced, and is also used to deal with vandalism, bots, personal attacks, and inappropriate usernames. '''Blocking''' is a technical means by which an account, IP address/range, or person is prevented from editing Misplaced Pages. For admins and bureaucrats, some of their additional privlidges are also affected by blocking.


Blocks are most frequently used to deal with vandalism and to enforce bans. There are other less common situations where blocks are appropriate, which are listed below. In all cases, blocks are preventative rather than punative, and serve only to avoid damage to Misplaced Pages. Blocks normally last 24 hours unless specified otherwise below, and in most instances will be lifted if the editor agrees to stop the damaging behavior.
There are three types of blocks:
*User accounts, which affect one person; <!-- Shouldn't this say "account" ? -->
*Anonymous ]es, which affect anyone sharing that IP address (in rare cases, a whole country);
*IP ranges, which affect potentially hundreds or thousands of people.


] have the technical ability to block any of these for any period of time, but such blocks should follow our blocking policy. All users can post block requests at ] or the other venues listed below. This can result in quick action where given credible evidence of policy violations, however admins are never obliged to place a block.

Normal users can post block requests at ] or ] for quick action in clear cases, giving credible evidence of policy violations. Admins are never obliged to place a block.


==When blocks may be used == ==When blocks may be used ==
Blocks are most frequently used to deal with ] and to enforce bans. There are several other less common situations where blocks are appropriate, which are listed below. Blocks should initially last 24 hours unless specified otherwise below.


===Vandalism=== ===Vandalism===
''Main article: ]'' ''Main article: ]''<br/>
''Report at ]''<br/>


Sysops may, at their judgement, block IP addresses whose users vandalise Misplaced Pages. For dynamic IPs, such blocks should last up to 24 hours. For static IPs, such blocks should initially last 24 hours, but repeat violators may be blocked for a maximum of one month; there are various ] by which sysops decide how far to extend the blocks of habitual vandals, none of which is formal policy. In general, casual vandals should be warned before being blocked, though warnings are not usually given for deliberate vandalism intended to discredit Misplaced Pages or serve an activist agenda. Sysops may block IP addresses whose users vandalise Misplaced Pages. There are various ] 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.

Logged-in users that do essentially nothing but vandalism may also be blocked for the same time periods. However, user accounts that perform a mixture of valid edits and vandalism should not be blocked in this manner.

Blocks should not be used against isolated incidents of vandalism.


=== Excessive reverts === === Excessive reverts ===
''Main article: ]'' ''Main article: ]''<br/>
''Report at ]''<br/>


Sysops may block users who violate the three revert rule. In the cases where multiple parties violate the rule, sysops should treat all sides equally. Sysops may block users who violate the three revert rule. Where multiple parties violate the rule, sysops will treat all sides equally.


=== Personal attacks which place users in danger ===
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.
''Main article: ]''


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 may be applied immediately by any sysop upon discovery.
Sysops blocked under this provision must not unblock themselves.

=== Bans ===
''Main article: ]''

Users that have been banned are typically blocked from editing Misplaced Pages. Such bans may occur as the result of:
* Community consensus that the user should be banned
* Ruling by the ]
* Ruling by ]
* Ruling by the ] ]

When it becomes clear that a user account is a "reincarnation" of an existing banned user, the reincarnating account can likewise be blocked. See ] for discussion. Blocks of reincarnations are almost always controversial.

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

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

The suggested block message is ].


===Disruption=== ===Disruption===
Sysops may block IP addresses or usernames that disrupt the normal functioning of Misplaced Pages. Such disruption may include changing other users' signed comments, making deliberately misleading edits, ], and excessive personal attacks. 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 will be reblocked if they continue being disruptive, or if they edit in a way which suggests they are likely to continue being disruptive.
Sysops may, at their judgement, block IP addresses or usernames that disrupt the normal functioning of Misplaced Pages. Such disruption may include changing other users' signed comments, making deliberately misleading edits, ], and excessive personal attacks. Users should normally be warned before they are blocked. 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. Blocks longer than a year typically require arbcom decisions.

Sysops may also block new user accounts that make lots of disruptive edits, for any length of time or permanently, at their discretion. ] that were created to violate Misplaced Pages policy should be blocked permanently. However, 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.

Reincarnations of blocked disruptive users will be reblocked if they continue being disruptive, or if they edit in a way which suggests they are likely to continue being disruptive.


Blocks under this provision may be controversial. Blocks under this provision may be controversial.
Line 77: Line 48:
''Main article: ]'' ''Main article: ]''


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. 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 ===
Usernames that are designed to impersonate legitimate users may be blocked immediately and indefinitely. 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.
''Main article: ]''


Users that have been banned are typically blocked from editing Misplaced Pages. Such bans may occur as the result of community consensus that the user should be banned, ruling by the ], ruling by ], or ruling by the ] ]
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.


When it becomes clear that a user account is a "reincarnation" of an existing banned user, the reincarnating account can likewise be blocked. See ] for discussion.
Sysops can force a namechange by blocking the username (with an expiry time of infinite). The blocking sysop should include ] in the block message (by writing <nowiki>{{UsernameBlock}}</nowiki> in the "reason" field), along with a link to the RfC or user talk page where the matter was discussed. If a user page has already been created, any user may add an explanation of why the user was blocked and a link to the ] page on the blocked user's userpage. It is not advisable to create user pages or talk pages for users with offensive usernames.


Blocks of reincarnations are almost always controversial.
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 ]. Click "unblock" next to that number. Then the user can log in under their new name.


===Users who exhaust the community's patience===
If an account has been blocked both for vandalism ''and'' for having an inappropriate username, the IP should be left ]


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 community support for the block, and should note the block on ] as part of the review process. With such support, the user is considered banned and should be listed on ] (under "Community").
=== "Public" accounts ===


=== "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, with the block message pointing out that public accounts are not needed.


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.
As an alternative, when confirming that the password is public, it is quite simple and often creates less fuss to just go into ] and change the password. This makes the password no longer public, and can also be done by anyone, not just an administrator.


=== Bots === === Bots ===
''Main article: ]'' ''Main article: ]''
Bots must have prior approval on ], and must follow certain minimum standards. In any case, sysops may block on sight any bot that appears to be out of control. Initial blocks should last 24 hours, which should be sufficient time to allow the operator of the bot to respond. Bots must have prior approval on ], and must follow certain minimum standards. In any case, sysops may block on sight any bot that appears to be out of control.


=== Personal attacks which place users in danger === === Anonymous and open proxies ===
''Main article: ]''


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: .
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 may be applied immediately by any sysop upon discovery. Sysops applying such sanctions should confidentially notify the members of the Arbitration Committee and Jimbo Wales of what they have done and why.


] was once used to automatically block open proxies, but was turned off as it "spooked" some people's ISPs.
===Users who exhaust the community's patience===


The suggested block message is ].
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 community support for the block, and should note the block on ] as part of the review process. With such support, the user is considered banned and should be listed on ] (under "Community").

==When blocking may not be used==

Use of blocks to gain advantage in a content dispute, and self-blocking to enforce a Wikiholiday or departure are specifically prohibited, although the latter was somewhat common earlier in our history. Likewise, users should not block those with whom they are currently engaged in an article-editing conflict. Generally, extreme caution should be exercised before blocking users acting in good faith.

Sysops should not block themselves (to enforce a "vacation" on themselves, for instance) because the resultant ] may affect other users (see ''Effects of being blocked'', below), unless they know what they're doing (i.e., they have a static IP).

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

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

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

# Check the facts with care.
# Reread appropriate parts of Misplaced Pages:Blocking policy.
# If possible, contact other administrators informally to be sure there are others who agree with your reasoning. The administrators' noticeboard, ] and email are effective tools for this.
# Place the block, exercising due care in the wording of the "reason" message, and include a link to the user page of the user being blocked.
# Place a notice of the block on the ] page of the affected user, with additional rationale, outlining the facts and the part of the blocking policy you feel applies.
# Be willing to discuss the block with other Wikipedians.

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.


== Effects of being blocked == == Effects of being blocked ==


Blocked users can still see all Misplaced Pages pages, but the "Edit this page" link brings up a "]" page which explains the reason behind the block and gives information on how to request unblocking. This page includes the "reason" message supplied by the administrator who placed the block. Links and template includes all work as normal in the "reason" section. Blocked users and a IP addresses can still see all Misplaced Pages pages, but the "Edit this page" link brings up a "]" page which explains the reason behind the block and gives information on how to request unblocking. This page includes the "reason" message supplied by the administrator who placed the block. Links and template includes all work as normal in the "reason" section.


The duration of the block depends on the expiry time that was entered at the time of the block, which may be "indefinite" or "infinite" (ie, until explicitly unblocked). The duration of the block depends on the expiry time that was entered at the time of the block, which may be "indefinite" or "infinite" (ie, until explicitly unblocked).
Line 145: Line 88:
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. 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 and bureaucrats, 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. Admins and bureaucrats should be careful not to unblock themselves in order to circumvent a block (unless it is an IP block to prevent vandalism), as a temporary revocation of administrator access ("desysopping") is the only way to ensure that this does not continue. For admins and bureaucrats, being blocked also restricts their ability to use rollback, to delete and undelete pages, and to protect and unprotect pages. They can still add and remove blocks, and bureaucrats can still make someone a sysop.


== Accidental blocks == == Accidental blocks ==
Line 153: Line 96:
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 accidentally 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 facade of untrustworthiness. Users who act so as to impersonate a previously banned user, to impersonate a known vandal, or to pretend to be engaging in vandalism, are also likely to be accidentally 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 facade of untrustworthiness.


== How to block == == Instructions to admins ==


===When blocking may not be used===

Use of blocks to gain advantage in a content dispute. Likewise, users should not block those with whom they are currently engaged in an article-editing conflict. Generally, extreme caution should be exercised before blocking users who may be acting in good faith.

Although the latter was somewhat common earlier in our history, self-blocking to enforce a Wikiholiday or departure are specifically prohibited. Sysops also should not block themselves for testing unless they they have a static IP because the resultant ] may affect other users.

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


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

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.

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.
=== Expiry times and application ===
Expiry times are entered in the GNU standard format, which is described in the . Alternatively, a block may be "indefinite" or "infinite", meaning the block is permanent, until a sysop explicitly unblocks the account. Expiry times are entered in the GNU standard format, which is described in the . Alternatively, a block may be "indefinite" or "infinite", meaning the block is permanent, until a sysop explicitly unblocks the account.


Line 165: Line 121:
A user may be blocked by more than one administrator at a time. In this case, the user will be blocked until his/her shortest block has expired. For instance, if an administrator blocks a user for one day, and another administrator blocks the same user for two days, then the user will remain blocked for one day, assuming that the blocks were given at the same time. A user may be blocked by more than one administrator at a time. In this case, the user will be blocked until his/her shortest block has expired. For instance, if an administrator blocks a user for one day, and another administrator blocks the same user for two days, then the user will remain blocked for one day, assuming that the blocks were given at the same time.


* Vandalism - For dynamic IPs, such blocks should last up to 24 hours. For static IPs, such blocks should initially last 24 hours, but repeat violators may be blocked for a maximum of one month;
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 ].
Logged-in users that do essentially nothing but vandalism may also be blocked for the same time periods. However, user accounts that perform a mixture of valid edits and vandalism should not be blocked in this manner. Blocks should not be used against isolated incidents of vandalism.

* Excessive reverts - 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.
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.
* 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. Blocks longer than a year typically require arbcom decisions. New accounts may be blocked for any length of time or permanently, and ] that were created to violate Misplaced Pages policy should be blocked permanently. However, 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. 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 namechange by blocking the username (with an expiry time of infinite). The blocking sysop should include ] in the block message (by writing <nowiki>{{UsernameBlock}}</nowiki> in the "reason" field), along with a link to the RfC or user talk page where the matter was discussed. If a user page has already been created, any user may add an explanation of why the user was blocked and a link to the ] page on the blocked user's userpage. It is not advisable to create user pages or talk pages for users with offensive usernames. 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 ]. 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 ] 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.
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.
*"Public" accounts - These should be with the block message pointing out that public accounts are not needed. As an alternative, when confirming that the password is public, it is quite simple and often creates less fuss to just go into ] and change the password. This makes the password no longer public, and can also be done by anyone, not just an administrator.
*Bots - 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 ===


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. 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.
Line 179: Line 138:
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 ]. 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 ].


== Unblocking == === Unblocking ===


] contains a list of all currently blocked users and IPs. Sysops will see a link to (<font color=blue></font>) next to each user. After clicking this, you should type in the reason that you are unblocking the user and then click the ''Unblock this address'' button. ] contains a list of all currently blocked users and IPs. Sysops will see a link to (<font color=blue></font>) next to each user. After clicking this, you should type in the reason that you are unblocking the user and then click the ''Unblock this address'' button.
Line 185: Line 144:
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, the safest course is to contact the blocking admin, another admin, or the mailing list and ask to be unblocked. 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, the safest course is to 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, please contact that admin to discuss the matter. Some reasons you might want to unblock would be: If you disagree with a block placed by another admin, please contact that admin to discuss the matter. Some reasons you might want to unblock would be:


Line 191: Line 149:
* The reason for the block no longer applies * The reason for the block no longer applies


Bear in mind that blocked users, especially troublemakers, commonly e-mail several admins claiming to be the victims of persecution by a biased admin. Because it is not always obvious from the blocked user's edit history what the problem was, '''it is a matter of courtesy and common sense to consult the blocking admin, rather than unblocking yourself'''. Bear in mind that blocked users commonly e-mail several admins claiming to be the victims of persecution by a biased admin. Because it is not always obvious from the blocked user's edit history what the problem was, '''it is a matter of courtesy and common sense to consult the blocking admin, rather than unblocking yourself'''.


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 you feel that such an error has been made, and the blocking admin is not available, you must notify the blocking admin on his or her talk page '''and''' the rest of the administrator community at Administrators' noticeboard/Incidents that you are unblocking a blocked user, '''before doing so'''. 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 you feel that such an error has been made, and the blocking admin is not available, you must notify the blocking admin on his or her talk page '''and''' the rest of the administrator community at Administrators' noticeboard/Incidents that you are unblocking a blocked user, '''before doing so'''.

Admins and bureaucrats should be careful not to unblock themselves in order to circumvent a block (unless it is an IP block to prevent vandalism), as a temporary revocation of administrator access ("desysopping") is the only way to ensure that this does not continue.

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

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

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

# Check the facts with care.
# Reread appropriate parts of Misplaced Pages:Blocking policy.
# If possible, contact other administrators informally to be sure there are others who agree with your reasoning. The administrators' noticeboard, ] and email are effective tools for this.
# Place the block, exercising due care in the wording of the "reason" message, and include a link to the user page of the user being blocked.
# Place a notice of the block on the ] page of the affected user, with additional rationale, outlining the facts and the part of the blocking policy you feel applies.
# Be willing to discuss the block with other Wikipedians.

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.




Revision as of 13:10, 21 January 2006

This page documents an English Misplaced Pages policy.It describes a widely accepted standard that editors should normally follow, though exceptions may apply. Changes made to it should reflect consensus.Shortcut
  • ]

Blocking is a technical means by which an account, IP address/range, or person is prevented from editing Misplaced Pages. For admins and bureaucrats, some of their additional privlidges are also affected by blocking.

Blocks are most frequently used to deal with vandalism and to enforce bans. There are other less common situations where blocks are appropriate, which are listed below. In all cases, blocks are preventative rather than punative, and serve only to avoid damage to Misplaced Pages. Blocks normally last 24 hours unless specified otherwise below, and in most instances will be lifted if the editor agrees to stop the damaging behavior.

All users can post block requests at Administrators' noticeboard/Incidents or the other venues listed below. This can result in quick action where given credible evidence of policy violations, however admins are never obliged to place a block.

When blocks may be used

Vandalism

Main article: Misplaced Pages: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

Main article: Misplaced Pages:three revert rule
Report at Administrators' noticeboard - 3RR

Sysops may block users who violate the three revert rule. Where multiple parties violate the rule, sysops will treat all sides equally.

Personal attacks which place users in danger

Main article: Misplaced Pages:No personal attacks

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

Disruption

Sysops may block IP addresses or usernames that disrupt the normal functioning of Misplaced Pages. Such disruption may include changing other users' signed comments, making deliberately misleading edits, harassment, and excessive personal attacks. 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 will be reblocked if they continue being disruptive, or if they edit in a way which suggests they are likely to continue being disruptive.

Blocks under this provision may be controversial.

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.

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)

Usernames

Main article: Misplaced Pages:username

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

Main article: Misplaced Pages:Banning policy

Users that have been banned are typically blocked from editing Misplaced Pages. Such bans may occur as the result of community consensus that the user should be banned, ruling by the 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 reincarnating account can likewise be blocked. See Misplaced Pages:Sock puppet for discussion.

Blocks of reincarnations are almost always controversial.

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 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 should be listed on Misplaced Pages:List of banned users (under "Community").

"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

Main article: Misplaced Pages: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 Template:Blocked proxy.

Effects of being blocked

Blocked users and a 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.

The duration of the block depends on the expiry time that was entered at the time of the block, which may be "indefinite" or "infinite" (ie, 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 and bureaucrats, 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 floating 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 accidentally 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 facade of untrustworthiness.

Instructions to admins

When blocking may not be used

Use of blocks to gain advantage in a content dispute. Likewise, users should not block those with whom they are currently engaged in an article-editing conflict. Generally, extreme caution should be exercised before blocking users who may be acting in good faith.

Although the latter was somewhat common earlier in our history, self-blocking to enforce a Wikiholiday or departure are specifically prohibited. Sysops also should not block themselves for testing unless they they have a static IP because the resultant "autoblock" may affect other users.

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.

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.

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.

A user may be blocked by more than one administrator at a time. In this case, the user will be blocked until his/her shortest block has expired. For instance, if an administrator blocks a user for one day, and another administrator blocks the same user for two days, then the user will remain blocked for one day, assuming that the blocks were given at the same time.

  • Vandalism - For dynamic IPs, such blocks should last up to 24 hours. For static IPs, such blocks should initially last 24 hours, but repeat violators may be blocked for a maximum of one month;

Logged-in users that do essentially nothing but vandalism may also be blocked for the same time periods. However, user accounts that perform a mixture of valid edits and vandalism should not be blocked in this manner. Blocks should not be used against isolated incidents of vandalism.

  • Excessive reverts - 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. Blocks longer than a year typically require arbcom decisions. 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, 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. 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 namechange 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. 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.
  • "Public" accounts - These should be with the 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, the safest course is to contact the blocking admin, another admin, or the mailing list and ask to be unblocked.

If you disagree with a block placed by another admin, please contact that admin to discuss the matter. Some reasons you might want to unblock would be:

  • The user was blocked in violation of this policy
  • The reason for the block no longer applies

Bear in mind that blocked users commonly e-mail several admins claiming to be the victims of persecution by a biased admin. Because it is not always obvious from the blocked user's edit history what the problem was, it is a matter of courtesy and common sense to consult the blocking admin, rather than unblocking yourself.

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 you feel that such an error has been made, and the blocking admin is not available, you must notify the blocking admin on his or her talk page and the rest of the administrator community at Administrators' noticeboard/Incidents that you are unblocking a blocked user, before doing so.

Admins and bureaucrats should be careful not to unblock themselves in order to circumvent a block (unless it is an IP block to prevent vandalism), as a temporary revocation of administrator access ("desysopping") is the only way to ensure that this does not continue.

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.

The most controversial blocks 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.

Categories: