CheckUser policy/gu

This page is a translated version of the page CheckUser policy and the translation is 11% complete.
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Esperanto • ‎Tiếng Việt • ‎Türkçe • ‎azərbaycanca • ‎català • ‎dansk • ‎español • ‎français • ‎hrvatski • ‎italiano • ‎kurdî • ‎magyar • ‎occitan • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎shqip • ‎sicilianu • ‎slovenčina • ‎svenska • ‎čeština • ‎български • ‎русский • ‎српски / srpski • ‎українська • ‎العربية • ‎मराठी • ‎हिन्दी • ‎ગુજરાતી • ‎മലയാളം • ‎中文 • ‎日本語 • ‎한국어
નીતિઓ અને માર્ગદર્શિકાઓ CheckUser policy
This page provides information about CheckUser access and outlines the policy on its use. It was discussed in September and October 2005, and went live in November 2005.
Meta-Wiki Checkuser-2000px.png

સભ્યતપાસક હોદ્દો

CheckUser is an interface for users with the checkuser permission. A user with the CheckUser permission on a wiki can, in particular, check if a user is a sockpuppet of another user on that wiki (not on all wikis). By using it, users are able to:

  • Determine from which IP addresses that an account has performed edits, logged actions, or password resets on the Wikimedia wiki;
  • Determine all edits, logged actions, and password resets that were performed on the Wikimedia wiki from a specific IP address (including users who were logged in with an account);
  • Determine whether the account being checked has sent an email using the MediaWiki interface to any other user. The time of the event is logged; the destination email address and destination account is obscured.

This information is only stored for a short period (currently 90 days), so edits made prior to that will not be shown via the CheckUser tool. A log is kept of who has made queries using the tool. This log is available to those with the checkuser-log permission:

See Help:CheckUser for the user manual.

Use of the tool

The tool is to be used to fight vandalism, spamming, to check for sockpuppet abuse, and to limit disruption of the project. It must be used only to prevent damage to any of the Wikimedia projects.

The tool should not be used for political control, to apply pressure on editors, or as a threat against another editor in a content dispute. There must be a valid reason to use the CheckUser tools to investigate a user. Note that alternative accounts are not forbidden, so long as they are not used in violation of the policies (examples of violations include double-voting, increasing the apparent support for any given position, or to evade blocks or bans).

Notification to the account that is checked is permitted but is not mandatory. Similarly, notification of the check to the community is not mandatory, but may be done subject to the provisions of the privacy policy.

Some wikis allow an editor's IPs to be checked upon his or her request if, for example, there is a need to provide evidence of innocence against a sockpuppet allegation; note, however, that requesting a checkuser in these circumstances is sometimes part of the attempt to disrupt.

ગોપનીયતા નીતિ

On Wikimedia projects, privacy policy considerations are of tremendous importance. Unless someone is violating policy with their actions (e.g. massive bot vandalism or spam) and revealing information about them is necessary to stop the disruption, it is a violation of the privacy policy to reveal their IP, whereabouts, or other information sufficient to identify them, unless they have already revealed this information themselves on the project.

Information release

Even if the user is committing abuse, it's best not to reveal personal information if possible.

  • Generally, do not reveal IPs. Only give information such as same network/not same network or similar. If detailed information is provided, make sure the person you are giving it to is a trusted person and will not reveal it himself/herself.
  • If the user has said they're from somewhere and the IP confirms it, it's not releasing private information to confirm it if needed.
  • If you're in any doubt, give no detail.


Access to CheckUser


Only stewards, ombuds, some Wikimedia Foundation staff, and a very small number of other users are allowed to have CheckUser access. Users can only have CheckUser status locally (except for the ombuds and those staff members with access).

If local CheckUsers exist in a project, checks should generally be handled by those. In emergencies, or for multi-project CheckUser checks (as in the case of cross-wiki vandalism), stewards may perform local checks. Stewards should remove their own CheckUser access on the projects upon completion of the checks and notify the local CheckUsers or the CheckUser e-mail list.

If no local Checkusers exist for a project, requests will need to be made to the stewards to perform checks (such as "is UserX a sockpuppet of UserY"). To do so, simply add the request to Steward requests/Checkuser listing these users and explain the need for the check (with links). Depending on the nature of the request, the steward may deny it, may ask for more information, or may answer about the likelihood of the users in question having the same IP, same proxy, same network, same country, or being completely unrelated (see discussion for what the Steward should more precisely say to the editor).

Appointing local Checkusers

On any wiki, there must be at least two users with CheckUser status, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one CheckUser is left on a wiki (when the only other one retires, or is removed), the community must appoint a new CheckUser immediately (so that the number of CheckUsers is at least two).

On wikis with an Arbitration Committee (ArbCom) whose members have been elected with the support of at least 25–30 members of the local community, CheckUsers may be directly appointed by the Arbitrators. After agreement, a member of the Committee should simply list the candidate on Steward requests/Permissions.

On a wiki without an Arbitration Committee that meets the criterion above, or in a project where there is a preference for independent elections, the community may approve local CheckUsers (stewards not counting as local CheckUsers) per consensus. The CheckUser candidate status must request it within the local community and advertise this request properly (village pump, mailing list when available, special request page, etc.). The candidate must be familiar with the privacy policy. After gaining consensus (at least 70%–80% in pro/con voting or the highest number of votes in multiple choice elections) in the local community, and with at least 25–30 editors' approval, the successful candidate should request access at Steward requests/Permissions with a link to the page with the community's decision. If there are an insufficient number of votes for at least two CheckUsers on a wiki, there will be no CheckUsers on that wiki.

Mailing list

There is a closed mailing list (CheckUser-l) to which all stewards and checkusers should have access. Email the list moderators to gain access. Use this mailing list to ask for help, ideas and second opinions if you're not sure what the data means.

IRC channel

There is a private IRC channel (#wikimedia-checkuserconnect) to which all stewards and checkusers who use IRC should have access. This channel serves the same purpose as the mailing list, but in real-time. Contact any channel member to gain access; a channel manager will grant permanent access. Ask a steward if you need help gaining access.

Removal of access

Any user account with CheckUser status that is inactive for more than one year will have their CheckUser access removed.

In case of abusive use of the tool, the Steward or the editor with the CheckUser privilege will immediately have their access removed. This will in particular happen if checks are done routinely on editors without a serious motive to do so (links and proofs of bad behavior should be provided).

Suspicion of abuses of CheckUser should be discussed by each local wiki. On wikis with an approved ArbCom, the ArbCom can decide on the removal of access. On wikis without an approved ArbCom, the community can vote removal of access.

Complaints of infringement of CheckUser, Access to Nonpublic Information Policy or Privacy Policy breaches are handled by the Ombuds commission for all Wikimedia projects.

સભ્યતપાસક અધિકાર ધરાવતા સભ્યો

  • Edit (last updated: 2020-10-24)


Everywhere

Arabic Wikipedia

Automatically generated checkusers list

  1. Elph
  2. Meno25
  3. باسم
  4. جار الله
  5. علاء
  6. فيصل

Bengali Wikipedia

Automatically generated checkusers list
Local policy mandates that only users who gain at least 25 votes in favor and 80% support can be appointed (application will open for no less than 30 days).

  1. আফতাবুজ্জামান
  2. NahidSultan

Catalan Wikipedia

Automatically generated checkusers list

  1. Góngora
  2. KRLS

Czech Wikipedia

Automatically generated checkusers list

  1. Jagro
  2. Martin Urbanec
  3. Mormegil

Danish Wikipedia

Automatically generated checkusers list

  1. Kaare
  2. KnudW
  3. Sir48

Dutch Wikipedia

Automatically generated checkusers list

Appointed by Arbcom
  1. Akoopal
  2. Ellywa
  3. Groucho NL
  4. Japiot
  5. Jcb

English Wikibooks

Automatically generated checkusers list

  1. QuiteUnusual
  2. Xania

English Wikipedia

Automatically generated checkusers list

Appointed by ArbCom
  1. AGK
  2. Alison
  3. AmandaNP
  4. Beeblebrox
  5. Berean Hunter
  6. Bradv
  7. Callanecc
  8. Casliber
  9. David Fuchs
  10. DGG
  11. Doug Weller
  12. Drmies
  13. EdJohnston
  14. GorillaWarfare
  15. Guerillero
  16. Ivanvector
  17. Joe Roe
  18. Jpgordon
  19. KrakatoaKatie
  20. L235
  21. Mailer diablo
  22. Materialscientist
  23. Maxim
  24. Mkdw
  25. MusikAnimal
  26. Mz7
  27. Newyorkbrad
  28. NinjaRobotPirate
  29. Oshwah
  30. PhilKnight
  31. Ponyo
  32. Reaper Eternal
  33. Risker
  34. Salvio giuliano
  35. SoWhy
  36. SQL
  37. ST47
  38. Stwalkerster
  39. TonyBallioni
  40. Versageek
  41. Worm That Turned
  42. Xeno
  43. Yamla
  44. Zzuuzz
Founder
  1. Jimbo Wales

English Wiktionary

Automatically generated checkusers list

  1. Chuck Entz
  2. TheDaveRoss

Finnish Wikipedia

Automatically generated checkusers list

  1. Ejs-80
  2. Harriv
  3. Stryn

French Wikipedia

Automatically generated checkusers list

Appointed by ArbCom
  1. 0x010C
  2. Hexasoft
  3. Jean-Christophe BENOIST
  4. Linedwell
  5. Marc Mongenet

German Wikipedia

Automatically generated checkusers list
Under the local policy, CheckUsers are elected for a two year term.

  1. Alraunenstern
  2. Hephaion
  3. Karsten11
  4. Perrak
  5. Rax

Hebrew Wikipedia

Automatically generated checkusers list

  1. Deror avi
  2. Matanya
  3. בריאן
  4. יונה בנדלאק
  5. עוזי ו.

Hungarian Wikipedia

Automatically generated checkusers list (requests and policy)

  1. Bináris
  2. Csigabi
  3. Grin
  4. Pallerti
  5. Tgr

Indonesian Wikipedia

Automatically generated checkusers list

  1. Aldnonymous
  2. Bennylin
  3. Meursault2004
  4. Nohirara

Italian Wikipedia

Automatically generated checkusers list

  1. Ask21
  2. Elwood
  3. Gac
  4. L736E
  5. Melos
  6. Ruthven
  7. Sakretsu
  8. Shivanarayana
  9. Vituzzu

Japanese Wikipedia

Automatically generated checkusers list (policy)

  1. Bellcricket
  2. Infinite0694
  3. Penn Station
  4. Y-dash
  5. さかおり

Korean Wikipedia

Automatically generated checkusers list (policy and request)

  1. Dmthoth
  2. IRTC1015
  3. Sotiale
  4. 이강철

Malayalam Wikipedia

Automatically generated checkusers list (Policy and Requests)

  1. Kiran Gopi
  2. Razimantv

Persian Wikipedia

Automatically generated checkusers list

  1. Huji
  2. Ladsgroup
  3. Sahehco

Polish Wikipedia

Automatically generated checkusers list
Due to a new policy on the Polish Wikipedia, users who gain 85% of votes in favor may become CheckUsers

  1. Masti
  2. Nedops
  3. Ptjackyll
  4. Saper
  5. Wojciech Pędzich

Portuguese Wikipedia

Automatically generated checkusers list

Under the local policy, CheckUsers are elected with two year term.

  1. Conde Edmond Dantès
  2. Érico until 19:59, 27 November 2020
  3. EVinente
  4. SEPRodrigues
  5. Stanglavine
  6. Tks4Fish until 21:43, 11 January 2021

Russian Wikipedia

Automatically generated checkusers list

Appointed by ArbCom
  1. DR
  2. OneLittleMouse
  3. Q-bit array
  4. Wulfson
  5. Ле Лой

Serbian Wikipedia

Automatically generated checkusers list

  1. Djordjes
  2. Dungodung
  3. Обрадовић Горан

Simple English Wikipedia

Automatically generated checkusers list

  1. Bsadowski1
  2. Djsasso
  3. Eptalon
  4. Lofty abyss
  5. Operator873
  6. Peterdownunder
  7. Vermont

Slovene Wikipedia

Automatically generated checkusers list

  1. MZaplotnik
  2. Romanm

Spanish Wikipedia

Automatically generated checkusers list
Local policy mandates that only users who gain at least 30 votes in favor and 80% support can be appointed.

  1. Alhen
  2. Bernard
  3. Montgomery
  4. Rastrojo

Swedish Wikipedia

Automatically generated checkusers list

  1. Fluff
  2. Julle
  3. Tegel


Turkish Wikipedia

Automatically generated checkusers list

  1. Eldarion
  2. Elmacenderesi
  3. Uncitoyen

Ukrainian Wikipedia

Automatically generated checkusers list

Appointed by ArbCom
  1. NickK
  2. VictorAnyakin
  3. Стефанко1982

Vietnamese Wikipedia

Automatically generated checkusers list

  1. DHN
  2. Mxn

Wikimedia Commons

Automatically generated checkusers list

  1. Elcobbola
  2. Jameslwoodward
  3. Krd
  4. Magog the Ogre
  5. Trijnstel

Wikispecies

Automatically generated checkusers list

  1. Dan Koehl
  2. Faendalimas
  3. Koavf

Meta

Automatically generated checkusers list · (information page and requests page)

  1. Ajraddatz
  2. MarcoAurelio
  3. Trijnstel

Wikidata

Automatically generated checkusers list · (information page and requests page)

  1. BRPever
  2. Jasper Deng
  3. Sotiale
  4. علاء


આ પણ જુઓ