This is an old revision of this page, as edited by 203.26.16.66 (talk) at 04:02, 26 May 2005. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 04:02, 26 May 2005 by 203.26.16.66 (talk)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)Blocks should not be used
penis
Vandalism
Sysops may, at their judgement, block IP addresses that vandalise Misplaced Pages. For sexy IPs, such blocks should last 24 hours. For s
Shortcut- ]
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. |
Blocks are one of the technological means by which bans are enforced, and are also used to deal with vandalism, bots, and inappropriate usernames. Blocks should, initially, last 24 hours, except as noted below. tatic IPs, such blocks should initially last 24 hours, but repeat beast
may be blocked for a maximum of one month; there are various rules of thumb that sysops follow in how much to extend the blocks of habitual vandals, none of which are formal policy. In general, casual vandals should be warned twice before being blocked, though warnings are not usually given for deliberate vandalism intended to discredit Misplaced Pages or serve an activist agenda. See Dealing with vandalism for overall policy.
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.
Excessive reverts
Sysops may block users who violate the three revert rule by reverting any page more than three times within a period of 24 hours. In the cases where multiple parties vi There are three types of blocks:
- User accounts
- Anonymous INTERNET PROTOCOL's
- IP ranges.
Administrators have the technical ability to block any of these for any period of time, but s.uch blocks should follow our blocking policy.
When blocks may be used
Blocks are most frequently used to deal with vandalism and to enforce bans. There are several other less common situations where blocks are appropriate, which are listed below.
olate the rule, sysops should treat all sides equally.
It is helpful to leave a notice of the block, with links to the diffs that demonstrate the violation, on the user's talk page.
Sysops blocked under this provision must not unblock themselves.
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 (for example, the quickpoll process briefly used in the first half of 2004)
- Ruling by the Arbitration Committee
- Ruling by Jimbo Wales
- Ruling by the Wikimedia Board of Trustees (which has yet to happen)
When it becomes clear thatS a user account is SMELLS LIKE THE PENIS of an existing banned user, the reincarnating account can likewise be blocked. See Misplaced Pages:Sock puppet for discussion. Blocks of reincarnations almost always become controversial.
See banning policy.
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 and uncontroversial.
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:BlockedProxy.
Disruption
Sysops may, at their judgement, block IP addresses that disrupt the normal functioning of Misplaced Pages. Such disruption is to be objectively defined by specific policies, and may include changing other users' signed comments or making deliberately misleading edits. Users should be warned that they are violating policy 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 a maximum of one month.
Sysops may also block new user accounts that make lots of disruptive edits, for any length of time or permanently, at their discretion. 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.
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—such as "YOU CANT BLOCK ME!!11!!" or "JOIN ME IN MY FIGHT TO DESTRY WIKIPEDIA!1!!1!!"
Blocks under this provision are almost always controversial.
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.
ANLA.
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 wIf an account has been blocked wfor vandalism and for having an inappropriate wusername, w==== Impersonation ==== users may be blocked immediately and indefinitely. The IP address of these users shouwwwld be left autoblockwed. Accounts and w, and then can be blocked. ww Please be sure that the accounww is a w. Use common sense. If the suspected impersonators are vandalizing, flaming other users, ww w w VAGINA===Bots===
As discuwwssed in Misplaced Pages:Botsww, bots must have prwior won sight any bot that appears to be out of w. 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
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 ban for a period of time 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. See No personal attacks.
This provision is rarely used.
When blocking may not be used
The list above is widely considered to be an exhaustive list of the situations that warrant blocking. Blocking should not be used in any other circumstances, unless there is exceptional widespread community support.
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 conflict.
Sysops should not block themselves (to enforce a "vacation" on themselves, for instance) because the resultant "autoblock" may affect other users (see Effects of being blocked, below), unless they know what they're doing (i.e., they have a static IP).
Effects of being blocked
Blocked users 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 they are editing is "autoblocked," so that they 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 they last accessed a page.
Note that blocking does not in any way restrict any feature other than normal article editing: normal users can still read articles, as well as adjust their watchlists and user preferences. Administrators and bureaucrats can continue to use all of their respective features: add and remove blocks, roll back vandalism, make someone a sysop, etc. If an admin or bureaucrat is blocked for a content dispute (such as the three revert rule), he should be careful not to use these abilities in relation to the article or articles in question, as a temporary revocation of administrator access ("desysopping") is the only way to ensure thmay be "indefinite" or "inf== Range blocks ==
Range blocks are sometimes used when a vandal or disruptivwe user has been IP blocked on several occasions but responds by using a dwifferent IP address. In most cases, range blocks will affect at least some legitimate users. Twherefore, range blocks should only w The range block feature is difficult to use correctly because it requires an understanding of binary arithmetic. It has certain limitations inherent wblocks]].
Unblocking
[[Special:wbut should absolutely not do so. If an admin feels they werwe not blocked for a valid reason, the safest w:
- Thewy were blocked in viwolatiowwnw wwof thwiws w
- The rewason for wblocking no longer applies.wThere are no hard and fast guidelines on unblocking, hence the "in other appropriate cases" guidance. Sysops must use their common sense and good judgement. See [[Misplaced Pages:Controversial inite", meaning the block is permanent, until a sysop explicitly unblocks the account.
If you don't enter an expiry time, you will see an error message.
blocks]] for w== See also ==
- Special:Ipblocklist (a list of blocked users)
- Block log
- Block log archives
at this does not continue.
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.
WHATCANIDOABOUTTHERETARDS
Expiry times are entered in the GNU standard format, which is described in the tar manual. Alternatively, a block
Categories: