User:Fungster/Blocking policy draft

From Miraheze Meta, Miraheze's central coordination wiki
Page Module:Message box/cmbox.css has no content.

Blocking is the method by which administrators technically prevent users from editing Meta. 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 Meta, but cannot edit any page (including their own user pages), except (in most cases) their own user talk pages.

Types of blocks[edit source]

Normal block[edit source]

Normal blocks are blocks that are directed to users who are vandalism-prone, spamming, or inappropriately using multiple accounts (see the section below). More than half of the existing blocks are considered "normal blocks".

CheckUser blocks[edit source]

Without first consulting a CheckUser, administrators should not undo or alter any block that is specifically identified as a "checkuser" block, such as through the use of the {{checkuserblock}} or {{checkuserblock-account}} templates in the action summary. If an administrator believes that a checkuser block has been made in error, the administrator should first discuss the matter with the CheckUser in question, and if a satisfactory resolution is not reached, should email staff. A reversal or alteration of such a block without prior consultation may result in removal of permissions.

Oversight blocks[edit source]

Appeals of blocks that have been marked by an oversighter as oversight blocks should be sent to the oversight team via on the Stewards' noticeboard to be decided by Miraheze oversighters. Blocks may still be marked by the blocking oversighter as appealable only to the staff team. Unblocking or altering without consent of an oversighter may result in removal of permissions.

Grounds for blocking[edit source]

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

Protection[edit source]

A user may be blocked when necessary to protect the rights, property, or safety of Miraheze Meta, its users, or the public. A block for protection may be necessary in response to:

Disruption-only[edit source]

See also: User accounts policy

Some types of user accounts are considered disruptive and may be blocked without warning, usually indefinitely:

Open or anonymous proxies[edit source]

See also: No open proxies policy

Open proxies may be blocked on sight.

Non-static IP addresses or hosts that are otherwise not permanent proxies typically warrant blocking for a shorter period of time, as the IP address 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; in general, these proxies should not be blocked indefinitely without consideration.

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

Duration of blocks[edit source]

Definite blocks[edit source]

Definite blocks are blocks that are set to a fixed expiry date. Blocks should always be set to a definite block unless directed by a sysadmin or a steward.

Indefinite blocks[edit source]

Indefinite blocks are ones where the block's length of term has been set to 'indefinite' by the admin placing the block. Indefinite blocks are used to prevent a specific account from editing until further notice.

Range blocks[edit source]

Sometimes users with dynamic IP addresses may attack the wiki. In such cases, it is best to range block their IP address so even when changing their IP they still can't edit. For more information, see mw:Help:Range blocks.

Unblocking[edit source]

Special:BlockList contains a list of all currently blocked users and IPs. Admins will see a link to unblock next to each user. After clicking this, admins should type in the reason that they are unblocking the user and then click the Unblock this address button.

Guidelines for administrators[edit source]

  • Before posting a block, is is best to ask another local admin if you are not sure.
  • If the block is controversial, considering posting a discussion on the Community noticeboard.
  • If the consensus is to block, then the administrators should contact other administrators to discuss the block length. However, if the consensus is to lock the user, then an admin should email stewards(at) explaining the situation (see the section below.)
  • If there is no consensus to block or the consensus is not to block, then the discussion shall be closed as unsuccessful or withdrawn.

Global blocks[edit source]

GlobalBlocking is a MediaWiki extension available to stewards to prevent cross-wiki disruption from an IP address or a range of IP addresses. When an IP address or range of IP addresses is globally blocked, they are prevented from editing any public Miraheze wiki, even this wiki, and appeals should be sent to cvt(at)

Locks[edit source]

A Global lock is a way by which stewards can technically prevent accounts from logging into any wiki that Miraheze hosts (and thus, no editing can be done). When an account is locked, attempts to log into it fail on all Wikimedia projects. It is generally applied to vandalism-only accounts, spam-only accounts, long-term abuser sock accounts, compromised accounts, and though in rare cases (until global blocking is extended to named accounts) users who would be eligible for a global block are locked in this way as well, issues such as like cross-wiki abuse. The locking interface also offers the option of hiding the account name in all logs, for usernames that are impersonating, harassing or offensive.

Requests for global locks should be sent to staff(at)

See also[edit source]