Commons:Requests for checkuser

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Shortcuts: COM:CHECK • COM:RFCU • COM:SOCK

This is the place to request investigations of abuse of multiple accounts or of other circumstances that require use of checkuser privileges.

Requesting a check

These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments.
Request completed
Confirmed  Technically indistinguishable
Likely  Possilikely
Possible Unlikely
Inconclusive Unrelated
 No action Stale
Request declined
Declined Checkuser is not for fishing
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
 It looks like a duck to me Checkuser is not a crystal ball.
Information
Additional information needed Deferred to
 Doing…  Info

Please do not ask us to run checks without good reason; be aware of the following before requesting a check:

  1. Checkuser is a last resort for difficult cases; pursue other options first, such as posting on the administrator's noticeboard. (This is not a venue for requesting administrative action such as blocks or file clean-up.)
  2. Running a check will only be done to combat disruption on Commons, or as required to assist checkuser investigations on other Wikimedia wikis.
    • Valid reasons for running a check include, for example: vandalism where a block of the underlying IP or IP range is needed and suspected block evasion, vote-stacking, or other disruption where technical evidence would prevent or reduce further disruption.
    • Requests to check accounts already confirmed on other projects may be declined as redundant.
    • Requests to run a check on yourself will be declined.
  3. Evidence is required. When you request a check, you must include a rationale that demonstrates (e.g., by including diffs) what the disruption to the project is, and why you believe the accounts are related.
    • Requests to run a check without evidence or with ambiguous reasoning will result in delays or the request not being investigated.
  4. The privacy policy does not allow us to make a check that has the effect of revealing IP addresses.

Outcome

Responses will be brief in order to comply with Wikimedia privacy policy. Due to technical limitations, results are not always clear. Closed requests are archived after seven days.

Privacy concerns

If you feel that a checkuser request has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombuds commission.

If this page is displaying outdated contents even after you refresh the page in your browser, please purge this page's cache.

To request a check:

Cases are created on subpages of Commons:Requests for checkuser/Case.

Creating a request
  • Insert the name of the suspected sockpuppeteer (the main account or puppetmaster, not the sockpuppet!) in the box below, leaving out the "User:" prefix. Do not remove the text in the box, add to the end only.
  • Please explain/justify the request by saying what it is you suspect and why it is important that the check be carried out. Indicate the usernames you suspect, using {{checkuser}}. Please do not use this template in the section header, as that makes it difficult to read the account names. Include the diffs or links required to support the request and reason for it.
  • There are people to assist you and help with maintenance of the page. Just ask for help on the admin noticeboard if you really are stuck, or take your best shot and note that you weren't completely sure of what to say.
  • If a case subpage already exists, edit the existing page instead, either adding to the currently open section (if the case is not yet archived) or adding a new section to the top using {{subst:Commons:Requests for checkuser/Inputbox/Sample}} (if the case has been archived). When editing an existing case, be sure to list/transclude the subpage here.
Example
If you want to request a checkuser on User:John Doe, enter the text Commons:Requests for checkuser/Case/John Doe then click "Request a checkuser". You will be taken to a page where you can fill out the request. Please make your request there brief and concise.


Then transclude your subpage on the top of the list at Commons:Requests for checkuser and remove {{Checkuser requests to be listed}} from the top of the case subpage.

nothing found

Requests

[edit]

Susandema

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Nhutamphan first uploaded File:Mr. Tô Lâm 2024.jpg on August 5, then the sock master added the corresponding file on enwiki on August 15. A1Cafel (talk) 09:53, 15 August 2024 (UTC)[reply]

@A1Cafel: File:Mr. Tô Lâm 2024.jpg was added by Huyle92. Susandema's 15 August edit (correct diff) did not add Nhutamphan's file. What is the evidence connecting Nhutamphan to Susandema? Эlcobbola talk 13:01, 15 August 2024 (UTC)[reply]
Nhutamphan added a copyvio image on viwiki on July 20, and that file was uploaded by Susandema on July 17. --A1Cafel (talk) 13:48, 15 August 2024 (UTC)[reply]

Susandema

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: These accounts like to upload images related to Vietnamese politicians (particularly Tô Lâm), see their upload logs, and almost all of them are taken from external sources without permission). A1Cafel (talk) 04:24, 3 August 2024 (UTC)[reply]

  • @A1Cafel: please review:
    1. COM:RFCU ("Evidence is required. When you request a check, you must include a rationale that demonstrates [...] why you believe the accounts are related" (underline in original));
    2. The hat-note when creating a RFCU ("focus[e] on diffs of the alleged conduct" (bold in original) and "Checkusers will not make a case for you. (bold in original)); and
    3. The markup note ("We will not go searching for 'who are the socks of this user', we need specific suspicions with information on why they are suspected" (bold added)).
Requests with lacking or inadequate evidence are becoming a habit for you. Vague references to "images related to Vietnamese politicians" (with no file names as example) and "see their upload logs" are inadequate, and obviously so to anyone who has read the aforementioned guidance. If you do not provide diffs and/or links to specific files with rationales explaining the connection in the future, your requests will be declined. I have, once again, done your work for you and checked based on Vangiangphanbqp uploading File:Mr. Tô Lâm.jpg at 08:42, 27 July 2024, and Susandema adding it to w:List of presidents of Vietnam at 02:24, 28 July 2024. (This is an example of what appropriate evidence looks like.) It is the last time I will do it for you. Эlcobbola talk 13:37, 3 August 2024 (UTC)[reply]
I've not checked Tranguyencl or Lethuyduyen2k because, again, appropriate evidence has not provided. They are, of course, not on the same ranges as the confirmed accounts. If evidence is provided, I am happy to check. Эlcobbola talk 13:37, 3 August 2024 (UTC)[reply]
I think that's fair enough. However, @Elcobbola: those confirmed accounts are not yet blocked (except Tuoitrenews, which was blocked almost seven years ago). --A1Cafel (talk) 11:12, 5 August 2024 (UTC)[reply]
✓ Done All accounts blocked, all files deleted. Yann (talk) 18:18, 14 August 2024 (UTC)[reply]

ShkoDevAct

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Exhibits similar uploading behavior as Kerosene3, specifically uploading non-free images related to Iraq/Kurdistan. The sockmaster has already been globally blocked. Ckfasdf (talk) 02:14, 15 August 2024 (UTC)[reply]

A3cb1

[edit]
[edit]

Rationale, discussion and results

[edit]

Usual edit pattern. Please check also for other possible SP.--Friniate (talk) 16:42, 10 August 2024 (UTC)[reply]

Confirmed --Krd 12:49, 13 August 2024 (UTC)[reply]



SleepyHollowGuy1999

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: I had filed here where a user was uploading copyrighted (non-libre) derivative files and vandalizing the sub-pages of the administrator noticeboard that I have on my watchlist. - THV | | U | T - 01:05, 3 August 2024 (UTC); edited: 01:36, 3 August 2024 (UTC)[reply]

Well, I'm glad they deserved a block, but who's next? - THV | | U | T - 01:42, 3 August 2024 (UTC)[reply]
Checkuser is not for fishing and Checkuser is not a crystal ball.. Эlcobbola talk 13:13, 3 August 2024 (UTC)[reply]

I Kadékk Gilang

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: These appear to fit in with the pattern of edits (subject matter, timeline of a new account every few days, false claims of own work as CC-zero) for Category:Sockpuppets of I Kadékk Gilang, which is itself an admitted sock of en:Wikipedia:Sockpuppet investigations/YilevBot/Archive. Considering that they're incredibly prolific, I also suspect there are sleepers. The Squirrel Conspiracy (talk) 22:45, 30 July 2024 (UTC)[reply]

@Elcobbola: Thanks. The biggest giveaway for Elijah Mahoebessy is File:Eastern Sumatra Malay.png. Virtually all of the I Kadékk Gilang socks have these same two shades of blue linguistic maps of Southeast Asian languages. Between that, the date range of account activity, and the copyvios as CC-zero, I'd be comfortable with a DUCK block if that's not enough for a CU. The Squirrel Conspiracy (talk) 00:01, 31 July 2024 (UTC)[reply]
Compare that upload with File:Bali Aga dialect map.jpg by confirmed sock አምላክ ብቻ, File:Idioma Balinés.png by confirmed sock Alèxandroedeutchland, and File:Sumbawan languages.png by suspected sock Œka. The Squirrel Conspiracy (talk) 00:04, 31 July 2024 (UTC)[reply]
Maps with that colouration are in wide use. How do you rule out Elijah Mahoebessy merely mimicking a style they observed? I don't say they are or aren't a sock, of course, but I don't consider that data point alone to be sufficient for a check. Is there more? Эlcobbola talk 00:10, 31 July 2024 (UTC)[reply]
If anything Elijah Mahoebessy looks to me like Jellywings19; are you familiar with them? Are they or their socks blocked on Commons? Эlcobbola talk 00:20, 31 July 2024 (UTC)[reply]
For this reason I've checked Elijah Mahoebessy related to Jellywings19. Elijah Mahoebessy is Confirmed to be Dhivehi Man, which is blocked on id.wiki for abusing multiple accounts. While no master is named there, the edits significantly overlap with known socks Blackman Jr., Ree11, etc, which is good enough for me to consider this Jellywings19.
It is difficult to imagine that en.wiki, which has been tracking I Kadékk Gilang (w:Category:Wikipedia sockpuppets of YilevBot) and Jellywings19 as separate masters for years--including with SPIs (YilevBot; Jellywings19)--would not have combined them if they were the same. Indeed, on Commons they are on different ISPs, regions, and devices, so current information is that Elijah Mahoebessy is technically Unrelated to I Kadékk Gilang. Эlcobbola talk 18:21, 31 July 2024 (UTC)[reply]

For older requests, please see Commons:Requests for checkuser/Archives