Cấm toàn cầu

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Global blocks and the translation is 7% complete.

Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Nederlands • ‎Tiếng Việt • ‎Türkçe • ‎dansk • ‎español • ‎euskara • ‎français • ‎føroyskt • ‎italiano • ‎lietuvių • ‎magyar • ‎norsk bokmål • ‎occitan • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎suomi • ‎čeština • ‎македонски • ‎русский • ‎українська • ‎العربية • ‎فارسی • ‎پښتو • ‎ਪੰਜਾਬੀ • ‎ગુજરાતી • ‎中文 • ‎日本語 • ‎한국어
Correct.svg Trang này hiện chỉ là một bản nháp. Thông tin chi tiết liên quan đến trang có thể xem tại trang thảo luận.

Bảo quản viên biên dịch: Thông thường, bản nháp không nên để dịch thuật.

For other recent discussion and questions, see the Global blocks talk page.

Global blocks are ways to prevent an account or IP address from editing all Wikimedia wikis, for a time or indefinitely.

There are requests to block or ban a user on all Wikimedia wikis every few months (more frequently in 2011?). Currently there is no available tool that can do this except for global IP blocks (see below), but this is being worked on.

In the meantime, a global block of an account can be requested - and either implemented as:

  • a block by hand on all wikis where the account is active.
  • temporarily implemented as a global lock until global account blocking is possible (though this is discouraged, except in extreme cases).

Global IP blocks

As of 2012, IP blocking is the only form of global blocking that is technically possible. The GlobalBlocking extension can block an IP address or range (maximum of /16 in IPv4, maximum of /4 in IPv6) from editing all Wikimedia projects except Meta, and is only available to Tiếp viên. These are logged in the Global block log.

Globally blocked IP addresses that cause disruption on Meta are locally blocked.


While exceptions exist, these are the guidelines:

  • Global blocks should only be placed where a combination of page protection, local blocks, and other technical and non-technical measures would be ineffective, or inefficient.
  • Global blocks may be placed on IP addresses:
  • Who engage in widespread cross-wiki vandalism, where that cross-wiki vandalism would currently require the intervention of stewards (as opposed to allowing local communities to manage the vandalism).
  • Who engage in cross-wiki spamming, where the user shows clear disregard for external link policies of the respective wikis.
  • Who are otherwise blatantly disrupting multiple projects, and the local communities of those projects are unable to effectively manage the behaviour. This is not intended to cover "trolling" or similar behaviour.
  • Which are open proxies being used abusively on multiple projects such as spamming links or forum spamming, and which are not being extensively used for legitimate purposes.
  • Global blocks should be placed with the lowest expiry possible, while still remaining effective. All global blocks should have an expiry (none should be indefinite).
  • Global blocks should, wherever practicable and sensible, be placed with the anonymous only flag on. Remember that even in this case account creation from the blocked address(es) is prevented.
  • Global blocks will remove talk page access when the block is encountered.


Accounts which are "global IP block exempt" are exempted from these global blocks. They are still vulnerable to IP and IP range blocks made locally on individual wikis. To apply for global IP block exemption see Steward requests/Global permissions.

Local unblocking

Global IP blocks can be locally unblocked on specific wikis by any sysops on that wiki (Special:GlobalBlockWhitelist). Similarly, user accounts can be unblocked where they are caught within an IP block, such blocks can be overridden on the local wiki by granting a local IP block exemption (Special:UserRights).

Global user blocks

See also: Global bans
Correct.svg This section is currently a draft.

Global blocking of users would be similar to that for IPs, but would apply to a username (and optionally its recent IP as well). A feature request to enable the GlobalBlocking extension for named accounts is under discussion.

Criteria should include:

  • Causing trouble repeatedly far beyond any helpful contributions:
    • Exhausting the patience of numerous wiki communities, and threatens to do so again.
    • Alternating vandalism and trolling and/or other disruptive behavior with small amounts of good work.
  • Doing something to make them unwanted on any project:
    • Threatening or driving away contributors or others (for instance: harrassment, legal threats).
    • Engaging in deep and carefully-planned harm: adding repeated forgeries and copyvios.
  • Protecting wikis (and their communities) where the user is not blocked yet and which would be subject and consider themself damaged by future foreseeable actions of the user, while not being able to prevent them with local tools and processes.

General requirements that should all be met:

  • Numerous wikis are involved.
  • Multiple communities have imposed long term bans.
  • User is likely to continue behaviour on other wikis when blocked locally.

Deciding on global blocks

Correct.svg This section is currently a draft.

Requests or appeals should be made on the Global [un]block and [un]lock requests page.

A global ban should be discussed in its own RFC and mentioned widely on meta, and on all communities where the user is active in the local language. Notice should be given, at a minimum, wherever local bans are discussed - or on the village pump if no local process exists.

Xem thêm