Globale blokkeringer

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 32% complete.

Outdated translations are marked like this.
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 This page is currently a draft. More information pertaining to this may be available on the talk page.

Translation admins: Normally, drafts should not be marked for translation.

For andre nylige diskusjoner og spørsmål, vennligst se diskusjonssiden for globale blokkeringer.

Globale blokkeringer er måter å forhindre en konto eller IP-adresse i å redigere på alle Wikimedia-wikiene i et begrenset tidsrom eller på ubestemt tid.

Det kommer gjerne forespørsler om å blokkere eller utestenge brukere på alle Wikimedia-wikiene med noen måneders mellomrom. Per i dag er det ingen tilgjengelige verktøy som kan utføre dette med unntak av global IP-blokkering (se nedenfor), men det jobbes med å utvikle bedre metoder.

Globale IP-blokkeringer

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 Forvaltere or selected WMF staff in special groups like WMF Support and Safety. These are logged in the Global block log.

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

Retningslinjer

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.

Unntak

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.

Lokal avblokkering

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).

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.

Se også