User:Yair rand/blocking


 * This is what the blocking policy would look like if I were in charge. This is why I'm not in charge. (Almost entirely based off of the Wikipedia blocking policy.)

Blocking policy
The block tool should only be used to prevent edits that will, directly or indirectly, hinder or harm the progress of the English Wiktionary. It is a last resort, only used when other methods of stopping these edits will clearly not succeed.

Blocking is the method by which administrators may technically prevent users from editing Wiktionary. Blocks are used to prevent damage or disruption to Wiktionary, not to punish users. Blocks sometimes are used as a deterrent, to discourage whatever behavior led to the block and encourage a productive editing environment.

Purpose and goal
All blocks ultimately exist to protect the project from harm, and reduce likely future problems. When lesser measures are inadequate, or problematic conduct persists, appropriate use of a block can help achieve this in four important ways:

For the purposes of protection and encouragement, blocks may escalate in duration to protect Wiktionary while allowing for the cessation of disruptive editing and the return to respected editing.
 * 1) Preventing imminent or continuing damage and disruption to Wiktionary.
 * 2) Deterring the continuation of disruptive behavior by making it more difficult to edit.
 * 3) Encouraging a rapid understanding that the present behavior cannot continue and will not be tolerated.
 * 4) Encouraging a more productive, congenial editing style within community norms.

Common rationales for blocks
The following are some of the most common rationales for blocks.

As a rule of thumb, when in doubt, do not block.

Administrators should take special care when dealing with new users. Beginning editors are often unfamiliar with Wiktionary policy and convention, and so their behavior may initially appear to be disruptive. Responding to these new users with excessive force can discourage them from editing in the future.

Protection
A user may be blocked when necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public. A block for protection may be necessary in response to:
 * persistently making personal attacks;
 * making personal, professional or legal threats (including outside the Wiktionary site);
 * performing actions that place users in danger;
 * persistently violating copyrights;
 * accounts that appear to have been compromised, as an emergency measure.

Disruption
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:
 * persistent vandalism;
 * persistent gross incivility;
 * persistent harassment;
 * persistent spamming;
 * breaching the sock puppetry policy;

Disruption-only
Furthermore, 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 or outside their 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 Spam.

Open or anonymous proxies
Open or anonymous proxies may be blocked on sight.

Non-static IPs or hosts that are otherwise not permanent proxies typically warrant blocking for a shorter period of time, as the IP is likely to be reassigned, or the open proxy is likely to be closed. Many Tor proxies, in particular, are "exit nodes" for only a short time; these proxies should generally not be blocked indefinitely without consideration.

There is also a Wiktionary project, the Project on open proxies, which seeks to identify and block open proxy servers.

Evasion of blocks
An administrator may reset the block of a user who intentionally evades a block, and may extend the duration of the block if the user engages in further blockable behavior while evading the block. User accounts or IP addresses used to evade a block may also be blocked.

Explanation of blocks
Blocking is a serious matter. The community expects that blocks will be made with 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
Administrators must supply a clear and specific block reason which 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 also notify users when blocking them by leaving a message on their user talk page unless they have a good reason not to. It is often easier to explain the reason for a block at the time than it is to explain a block well after the fact.

When implementing a block, a number of pro forma block reasons are available in a drop-down menu; other or additional reasons can also be added.

Other important information
If there are any specific recommendations or circumstances that a reviewing administrator would need to know, or which may help to avoid administrator disputes upon review of a block, the blocking administrator should consider including this information in the block notice. For example:


 * When there is information or evidence that may not be obvious, may not be fully appreciated, or may otherwise be relevant.
 * Prior endorsement that if any administrator wishes to unblock, or there is consensus for it, they may without consulting the blocking administrator.
 * Suggested conditions for an unblock.

Education and warnings
Everyone was new once, and most of us made mistakes. That's why when we welcome newcomers, we are patient with them, and assume that most people who work on the project are trying to help it, not hurt it. We also ask that newcomers make an effort to learn about our policies and guidelines so that they can learn how to avoid making mistakes.

Before a block is imposed, efforts should be made to educate the user about our policies and guidelines, and to warn them when their behaviour conflicts with our policies and guidelines. A variety of template messages exist for convenience, although purpose-written messages are often preferable.

Warning is not a prerequisite for blocking (particularly with respect to blocks for protection) but administrators should generally ensure that users are aware of policies, and give them reasonable opportunity to adjust their behaviour accordingly, before blocking. Users who have been made aware of a policy and have had such an opportunity, and accounts whose main or only use is forbidden activity (sock-puppetry, obvious vandalism, personal attack, and so on) may not require further warning.