User:Kwj2772/Workstation/2

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Languages:
Policies and guidelines 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.

CheckUser status[edit]

체크유저는 체크유저 권한을 가진 사용자의 인터페이스입니다. 체크유저 권한을 가진 사용자는 해당 위키(모든 위키가 아닙니다.)에서 다중 계정을 사용하고 있지는 않은지 확인할 수 있습니다. 이것을 통해 다음을 할 수 있습니다:

  • 위키미디어 재단의 위키에 편집한 사용자의 IP를 볼 수 있습니다.
  • 특정 IP에서 누가 편집했는지 알 수 있습니다.
  • 누가, 그리고 언제 이메일을 보냈는지를 알 수 있고 이메일 주소도 확인할 수 있습니다.

이 정보는 단시간만 보존되고 삭제됩니다. 따라서 이전의 편집에 대한 정보는 체크유저를 통해 확인되지 않을 수 있습니다. 체크유저 기록은 누가 어떤 정보를 확인했는지에 대해 남게 됩니다. 이 로그는 체크유저 권한을 가진 사용자가 볼 수 있습니다.

2006년 9월 5일 17:29 $1 은(는) $2 이(가) 사용한 IP 주소를 열람했습니다.
2006년 9월 5일 17:29 $1 은(는) $2의 편집을 열람했습니다.

자세한 내용은 Help:CheckUser를 참고하십시오.

Use of the tool[edit]

The tool is to be used to fight vandalism, to check for sockpuppet abuse, and to limit disruption of the project. It must be used only to prevent damage to any of 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 check a user. Note that alternative accounts are not forbidden, so long as they are not used in violation of the policies (for example, to double-vote or to increase the apparent support for any given position).

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.

Privacy policy[edit]

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. The relevant section of the privacy policy is:

Policy on release of data derived from page logs
It is the policy of Wikimedia that personally identifiable data collected in the server logs, or through records in the database via the CheckUser feature, may be released by the system administrators or users with CheckUser access, in the following situations:
  1. In response to a valid subpoena or other compulsory request from law enforcement
  2. With permission of the affected user
  3. To the chair of Wikimedia Foundation, his legal counsel, or his designee, when necessary for investigation of abuse complaints.
  4. Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues.
  5. Where the user has been vandalising articles or persistently behaving in a disruptive way, data may be released to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers
  6. Where it is reasonably necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public.

Information release[edit]

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.
  • 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[edit]


Only Stewards and a very few editors are allowed to have the CheckUser status. Editors will only have CheckUser status locally.

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 CheckUser access on the projects upon completion of the checks and notify the local CheckUsers or the CheckUser e-mail list.

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 can be appointed by the Arbitrators only. 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 where the community prefers independent elections, two options are possible:

The community must approve CheckUsers per consensus. The user requesting CheckUser status must request it within his local community and advertise this request properly (village pump, mailing list when available, ...). The editor must be familiar with the privacy policy. After gaining consensus (at least 70%-80%) in his local community, and with at least 25-30 editors' approval, the user should list himself under Steward requests/Permissions with a link to the page with the community's decision.
If an insufficient number of voters vote for at least two CheckUsers on a wiki, there will be no CheckUser on that wiki. Editors will have to ask a Steward to check if UserX is a sockpuppet of UserY. To do so, simply add your request to Steward requests/Checkuser listing these users and explaining why you ask for such a check (with links). You also need a community consensus (like above). The Steward will answer you if these two users are from the same IP, same proxy, same network, same country, or are they completely unrelated (see discussion for what the Steward should more precisely say to the editor).


Mailing list[edit]

For Wikimedia CheckUser users, there is a mailing list, CheckUser-l. This is a closed list. Use this list to ask for help, ideas and second opinions if you're not sure what the data means. All users with CheckUser access should be a member of the list.

Removal of access[edit]

Any user account with CheckUser status that is inactive for more than a year will have their CheckUser access be 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. Removal can only be done by Stewards. A Steward may not decide to remove access on their own, but can help provide information necessary to prove the abuse (such as logs). If necessary, and in particular in case of lack of respect towards the privacy policy, the Board of Wikimedia Foundation can be asked to declare removal of access as well.

Complaints of abuse of CheckUser or privacy policy breaches may also be brought to the Ombudsman committee.

Current users with access[edit]

  • Edit (last updated: 2022-09-20)

Everywhere[edit]

Arabic Wikipedia[edit]

Automatically generated checkusers list

  1. Dr-Taher
  2. Meno25
  3. باسم
  4. جار الله
  5. صالح
  6. علاء
  7. فيصل

Bengali Wikipedia[edit]

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. Al Riaz Uddin Ripon
  2. NahidSultan

Catalan Wikipedia[edit]

Automatically generated checkusers list

  1. Jmrebes
  2. Joutbis
  3. KRLS

Czech Wikipedia[edit]

Automatically generated checkusers list

  1. Jagro
  2. Martin Urbanec
  3. Mormegil

Danish Wikipedia[edit]

Automatically generated checkusers list

  1. Kaare
  2. KnudW
  3. Sir48

Dutch Wikipedia[edit]

Automatically generated checkusers list

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

English Wikibooks[edit]

Automatically generated checkusers list
(Local policy mandates that Stewards are explicitly allowed to process non-emergency CheckUser requests)

  1. MarcGarver
  2. Xania

English Wikinews[edit]

Automatically generated checkusers list

  1. Acagastya
  2. Cromium

English Wikipedia[edit]

Automatically generated checkusers list

Appointed by ArbCom
  1. Alison
  2. AmandaNP
  3. BDD
  4. Barkeep49
  5. Beeblebrox
  6. Bradv
  7. Cabayi
  8. CaptainEek
  9. Donald Albury
  10. Doug Weller
  11. Dreamy Jazz
  12. Drmies
  13. EdJohnston
  14. Enterprisey
  15. Ferret
  16. GeneralNotability
  17. Girth Summit
  18. Guerillero
  19. Izno
  20. Joe Roe
  21. Jpgordon
  22. KrakatoaKatie
  23. Ks0stm
  24. L235
  25. Mailer diablo
  26. Materialscientist
  27. Maxim
  28. Mkdw
  29. MusikAnimal
  30. Mz7
  31. NinjaRobotPirate
  32. Opabinia regalis
  33. Oshwah
  34. PhilKnight
  35. Ponyo
  36. Primefac
  37. Reaper Eternal
  38. Risker
  39. RoySmith
  40. SQL
  41. ST47
  42. Salvio giuliano
  43. Stwalkerster
  44. TheresNoTime
  45. TonyBallioni
  46. Versageek
  47. Worm That Turned
  48. Wugapodes
  49. Yamla
  50. Zzuuzz
Founder
  1. Jimbo Wales

English Wiktionary[edit]

Automatically generated checkusers list

  1. Chuck Entz
  2. TheDaveRoss

Finnish Wikipedia[edit]

Automatically generated checkusers list

  1. Ejs-80
  2. Harriv
  3. Stryn

French Wikipedia[edit]

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

  1. 3(MG)²
  2. Hexasoft
  3. Hyméros
  4. Linedwell
  5. Marc Mongenet
  6. Poudou!

German Wikipedia[edit]

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

  1. Der-Wir-Ing
  2. Karsten11
  3. Perrak

Hebrew Wikipedia[edit]

Automatically generated checkusers list

  1. Deror avi
  2. Matanya
  3. TheStriker
  4. יונה בנדלאק
  5. דגש

Hungarian Wikipedia[edit]

Automatically generated checkusers list (requests and policy)

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

Indonesian Wikipedia[edit]

Automatically generated checkusers list

  1. Bennylin
  2. David Wadie Fisher-Freberg
  3. Hidayatsrf
  4. Meursault2004
  5. Nohirara

Italian Wikipedia[edit]

Automatically generated checkusers list

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

Japanese Wikipedia[edit]

Automatically generated checkusers list (policy)

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

Korean Wikipedia[edit]

Automatically generated checkusers list (policy and request)

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

Malayalam Wikipedia[edit]

Automatically generated checkusers list (Policy and Requests)

  1. Kiran Gopi
  2. Razimantv

Persian Wikipedia[edit]

Automatically generated checkusers list

  1. Huji
  2. Ladsgroup

Polish Wikipedia[edit]

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. Saper
  4. Wojciech Pędzich

Portuguese Wikipedia[edit]

Automatically generated checkusers list

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

  1. Albertoleoncio
  2. Conde Edmond Dantès
  3. Érico
  4. Stanglavine
  5. Tks4Fish

Russian Wikipedia[edit]

Automatically generated checkusers list

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

Serbian Wikipedia[edit]

Automatically generated checkusers list

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

Simple English Wikipedia[edit]

Automatically generated checkusers list

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

Slovene Wikipedia[edit]

Automatically generated checkusers list

  1. MZaplotnik
  2. Romanm

Spanish Wikipedia[edit]

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. BlackBeast
  4. LuchoCR
  5. Montgomery
  6. Rastrojo

Swedish Wikipedia[edit]

Automatically generated checkusers list

  1. Fluff
  2. Julle
  3. Tegel

Thai Wikipedia[edit]

Automatically generated checkusers list

  1. Geonuch
  2. Timekeepertmk

Turkish Wikipedia[edit]

Automatically generated checkusers list

  1. Elmacenderesi
  2. Uncitoyen
  3. Vincent Vega

Ukrainian Wikipedia[edit]

Automatically generated checkusers list

Appointed by ArbCom
  1. Andriy.v
  2. Goo3
  3. Mykola7
  4. NickK

Vietnamese Wikipedia[edit]

Automatically generated checkusers list

  1. DHN
  2. Mxn

Wikimedia Commons[edit]

Automatically generated checkusers list

  1. Elcobbola
  2. Fitindia
  3. Jameslwoodward
  4. Krd
  5. Trijnstel

Wikispecies[edit]

Automatically generated checkusers list

  1. Dan Koehl
  2. Faendalimas
  3. Koavf

Meta[edit]

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

  1. Ajraddatz
  2. Hasley
  3. MarcoAurelio
  4. Minorax
  5. Sotiale
  6. Trijnstel
  7. Vermont
  8. Xaosflux

Wikidata[edit]

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

  1. 1997kB
  2. BRPever
  3. Jasper Deng
  4. Sotiale
  5. علاءaccess

See also[edit]