This is a Wiktionary policy, guideline or common practices page. The portion of it which is policy may not be modified without a VOTE. | |
Policies – Entries: CFI - EL - NORM - NPOV - QUOTE - REDIR - DELETE. Languages: LT - AXX. Others: BLOCK - BOTS - VOTES. |
This policy page consists of two sections: (a) policy, the statement of binding policy; (b) explanation, a non-binding explanation of the policy, and guidelines showing how the policy is usually applied. The only binding section is “policy”. The section “policy” is not merely the policy in a nutshell but rather the complete statement of the policy itself.
The blocking policy itself is as follows:
There is deliberately no hard-and-fast rule about what is considered to hinder or harm our progress. Clear examples of such behaviour include:
There are few other means of protecting Wiktionary; the most obvious is by discussion on the users’ talk pages. Some effort should be made to explain to people why their edits are considered incorrect, however a short block can be given if they clearly won’t listen. In cases where a user has had something explained to them, an explicit warning should be given to them before blocking them; this can show that they have no intention of mending their ways.
When patrolling recent changes, it is likely you will want to block some users instantly, normally when they clearly have no intent to be productive.
Particularly:
However, there are people who make innocent mistakes; they should not be blocked instantly:
Such an account can be blocked if its user ignores a single request to desist or explanation of what that user is doing wrong.
It is rare, but occasionally there will be a seasoned contributor, even an administrator, who is causing trouble; such cases must be handled with diplomacy. It is not acceptable to block a whitelisted user or an administrator unless they already know they will be blocked for their actions. In most cases they will not know they will be blocked unless they have received an explicit warning or are deliberately and maliciously ignoring current practice.
Logged in accounts: | Anonymous editors only | Prevent account creation | |
---|---|---|---|
infinite |
|
N/A | N/A |
> 1 month | Third blocks for persistent or repeat offenders. | N/A | N/A |
7–31 days | Second blocks for persistent or repeat offenders. | N/A | N/A |
1–7 days | Primary blocks for behavior which is counter to policy, productivity or community. | N/A | N/A |
<24 hours | These blocks should rarely be given out, but if attempts to communicate with another community member fail, a very short term block can be issued. | N/A | N/A |
For anonymous IP addresses, the 99% case is non-recurring stupidity. Don’t waste your time doing research on the IP if the IP has not been blocked before: block one day, anon-users/prevent-creation only. If it recurs (block log has entries), then look closer:
Anonymous contributors: static or semi-static vs. dynamic IPs | Anonymous editors only | Prevent account creation | |
---|---|---|---|
infinite | Never. Open proxies and zombies are blocked globally not locally. | NO! | YES! |
>1 month | IPs which have been blocked for shorter durations before, and have returned: probable static IPs. | No | YES |
7–31 days | Vandalism which would be blocked for this duration on a registered account, on what is probably a static IP. | No | Yes |
1–7 days | Most anonymous vandalism which is from DSL/Cable ISP (SBC/Comcast/RR) IPs. | Yes | Yes |
<24 hours | Large ISP (AOL/BT) IPs engaged in any sort of vandalism. | Yes | No |
See Wiktionary:Range blocks for when and how to block a range of IP addresses.
As of 17 June, 2019 it is possible to block users from editing specific pages or a specific namespace.
See Community health initiative/Partial blocks at meta.wikimedia for more.
Blocked users can request unblocking by posting a filled-out {{Template:unblock}}
on their own user talk page. Uninvolved editors may discuss the block, and the blocking administrator may be asked to comment. Because the purpose of an unblock request is to obtain review from a third party, blocking administrators should not decline unblock requests from users they have blocked, but except in cases of unambiguous error or significant change in circumstances, administrators should avoid unblocking without first attempting to contact the blocking administrator to discuss the matter. If the blocking administrator is not available, or if cannot come to an agreement, a discussion at the Beer parlour is recommended.