|This policy from Wikipedia is so good, we use it. Click here to see the original.
They're doing pretty well, maybe we can learn a thing or two...
|This page is relevant for administrators.|
Are these pages relevant to you: No, you're not an admin.
|This page in a nutshell: Just slap 'em with an indefinite block|
Blocking is the method by which administrators technically prevent users from editing EndMyopia Wiki. Blocks may be applied to user accounts, to IP addresses, and to ranges of IP addresses, for either a definite or an indefinite time. Blocked users can continue to access EndMyopia Wiki, but cannot edit any page), except (in most cases) their own user talk pages.
Blocks are used to prevent damage or disruption to EndMyopia Wiki, not to punish users. Any user may report disruption and ask administrators to consider blocking a disruptive account or IP address.
If editors believe a block has been improperly issued, they can request a review of that block on their own talk page. Administrators can "unblock" a user when they feel the block is unwarranted or no longer appropriate.
- 1 EndMyopia Wiki: The blocking policy
- 2 The philosophy of blocking (this also applies, but it's incredibly long and thorough and you probably shouldn't bother reading any of this)
- 2.1 Blocks should not be punitive
- 2.2 Blocks should be preventative
- 2.3 Common rationales for blocks
- 2.4 When blocking may not be used
- 2.5 Against the blocking administrator
- 2.6 Blocking
- 2.7 Explanation of blocks
- 3 Technical tools
EndMyopia Wiki: The blocking policy
If someone's clearly vandalising the wiki,
slap give the user an indefinite block on the default settings for blocking.
If it's not clear that it's vandalism, hold out and assume good faith, reverting edits as appropriate. We don't want to chase away new editors.
The philosophy of blocking (this also applies, but it's incredibly long and thorough and you probably shouldn't bother reading any of this)
Blocks serve to protect the project from harm, and reduce likely future problems. Blocks may escalate in duration if problems recur. They are meted out not as retribution but to protect the project and other users from disruption and inappropriate conduct, and to deter any future possible repetitions of inappropriate conduct. Blocking is one of the most powerful tools that are entrusted to administrators, who should be familiar with the circumstances prior to intervening and are required to be able to justify any block that they issue.
Blocks should not be punitive
Blocks should not be used:
- to retaliate;
- to disparage;
- to punish; or
- if there is no current conduct issue of concern.
Blocks should be preventative
Blocks should be used to:
- prevent imminent or continuing damage and disruption to EndMyopia Wiki;
- deter the continuation of present, disruptive behavior; and
- encourage a more productive, congenial editing style within community norms.
Deterrence is based upon the likelihood of repetition. For example, though it might have been justifiable to block an editor a short time ago, such a block may no longer be justifiable right now, particularly if the actions have since ceased or the conduct issues have been resolved.
Common rationales for blocks
"Not here to build a vision improvement encyclopedia"
This hopefullly most used blocking rationale is described at EM:Here to build a vision improvement encyclopedia § Clearly not being here to build a vision improvement encyclopedia.
A user may be blocked when necessary to protect the rights, property, or safety of its users, or the public. A block for protection may be necessary in response to:
- persistent personal attacks;
- personal, professional, or legal threats (including outside the Wikipedia site);
- actions placing users in danger;
- actions that may compromise the safety of children
- disclosures of others' personal information (whether or not the information is accurate);
- persistent copyright violations;
- persistent posts of unreferenced, poorly or incorrectly referenced, or potentially Wikipedia:defamatory information about living persons; or
- an account appearing to have been compromised (as an emergency measure), i.e. there is some reason to believe the account is being used by someone other than the person who registered the account.
A user may be blocked when his or her conduct severely disrupts the project; that is, when his or her conduct is inconsistent with a civil, collegial atmosphere and interferes with the process of editors working together harmoniously to create an encyclopedia. A block for disruption may be necessary in response to:
- gross incivility;
- edit warring, especially breaches of the three-revert rule;
- deliberately tripping the abuse filter
- breaching the policies or guidelines, especially the sock puppetry policy;
- attempts to coerce actions of editors through threats of actions outside the EndMyopia community, whether onsite or offsite.
Some types of user accounts are considered disruptive and may be blocked without warning, usually indefinitely:
- Accounts used exclusively for disruptive purposes, such as vandalism.
- Public accounts (where the password is publicly available or shared with a large group).
- Accounts with inappropriate usernames.
- Bots operating without approval.
- Accounts that appear, based on their edit history, to exist for the sole or primary purpose of promoting a person, company, product, service, or organization. See EM:Conflict of interest and EM:Spam.
When blocking may not be used
Conflicts and involvement
Administrators must not block users with whom they are engaged in a content dispute; instead, they should report the problem to other administrators. Administrators should also be aware of potential conflicts involving pages or subject areas with which they are involved. It is acceptable for an administrator to block someone who has been engaging in clear-cut vandalism in that administrator's userspace.
Blocks intended solely to "cool down" an angry user should not be used, as they often have the opposite effect. However, an angry user who is also being disruptive can be blocked to prevent further disruption.
Recording in the block log
Blocks should not be used solely for the purpose of recording warnings or other negative events in a user's block log. The practice, typically involving very short blocks, is often seen as punitive and humiliating.
Very short blocks may be used to record, for example, an apology or acknowledgement of mistake in the block log in the event of a wrongful or accidental block, if the original block has expired. (If it has not, the message may be recorded in the unblocking reason.)
Against the blocking administrator
A blocked administrator can block the blocking administrator, but should only do so in exceptional circumstances where there is a clear and immediate need, such as in the case of a compromised account. Use of the block tool to further a dispute or retaliate against the original blocking administrator is not allowed.
Preliminary: education and warnings
Before a block is imposed, efforts should be made to educate users about EndMyopia Wiki policies and guidelines, and to warn them when their behavior conflicts with these. Welcome newcomers, do not bite them, and assume that most people who work on the project are trying to help it, not hurt it. Newcomers should make an effort to learn about our policies and guidelines so that they can learn how to avoid making mistakes.
However, warnings are not a prerequisite for blocking. In general, administrators should ensure that users who are acting in good faith are aware of policies and are given reasonable opportunity to adjust their behavior before blocking, and it may be particularly desirable to communicate first with such users before blocking. On the other hand, users acting in bad faith, whose main or only use is forbidden activity (sockpuppetry, vandalism, and so on), do not require any warning and may be blocked immediately.
Explanation of blocks
Blocking is a serious matter. The community expects that blocks will be made for good reasons only, based upon reviewable evidence and reasonable judgment, and that all factors that support a block are subject to independent peer review if requested.
Notifying the blocked user
must preferably would supply a clear and specific block reason that indicates why a user was blocked. Block reasons should avoid the use of jargon as much as possible so that blocked users may better understand them. Administrators should notify users when blocking them by leaving a message on their user talk page. It is often easier to explain the reason for a block at the time than it is to explain a block well after the event.