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.

Checkuser requests to be listed‎ (empty)
nothing found

Requests[edit]

Eka343[edit]

Status: open • view • edit • history • watch
Filed: 23:11, 22 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Suspicion of (not allowed) self-promotions of Quality Images nominations: see this edit by Damayantidwi, where they are promoting several QI nominations in one edit, of which three previously were submitted by Eka343. Before this edit, Damayantidwi never had participated on QIC and had made only about 35 Commons edits in total. A CU request on both was suggested by SHB2000 here, following this I pinged Eka343 for statement, yet no response and also no activities on Commons since then. Note also that both Eka343 [1] and Damayantidwi [2] are/were relatively active on "ban.wikisource", which makes a relation (up to sockpuppetry) even more likely. Thanks --A.Savin 23:11, 22 January 2024 (UTC)Reply[reply]

To add, ban.wikisource is a very small wiki as well. --SHB2000 (talk) 23:33, 22 January 2024 (UTC)Reply[reply]

Nipponese Dog Calvero[edit]

Status: open • view • edit • history • watch
Filed: 08:55, 22 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The very same behavior—insists on trying to rename this file even though their request has been already denied countless times. RodRabelo7 (talk) 08:51, 22 January 2024 (UTC)Reply[reply]


7-cm Mr Chung from Hong Kong[edit]

Status: open • view • edit • history • watch
Filed: 05:00, 22 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: I know chekcuser is not fishing and I will understand if this request is denied, but due to the extent of the disruption caused by this account and due to the obvious fact that this is a sock and an attack-only account, I need to try. This is account was created solely to attack Wilfredor (talk · contribs) and A1Cafel (talk · contribs). Please see Commons:Deletion requests/Files in Category:Featured pictures by User:Wilfredor for more context. Kacamata! Dimmi!!! 05:00, 22 January 2024 (UTC)Reply[reply]

I don't know what was in the editions, if someone could provide the information that was written there it could give me more clues as to who it was. If it was just rudeness it is not necessary. I'd like to look ahead to see where this all leads. --Wilfredor (talk) 10:46, 22 January 2024 (UTC)Reply[reply]
  • Checkuser is not for fishing. Эlcobbola talk 12:27, 22 January 2024 (UTC)Reply[reply]
    When I refer to what I would like to see, I am referring to the hidden comments from the history. Wilfredor (talk) 23:41, 22 January 2024 (UTC)Reply[reply]

Jurisdrew[edit]

Status: open • view • edit • history • watch
Filed: 18:08, 21 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: All brand new accounts uploading various attributed flags, some of which may be legitimate but most of which appear extremely dubious. Also following similar file naming schemes as the original Jurisdrew account. I believe this falls under the duck test, but we might as well do it the right way. Fry1989 eh? 18:08, 21 January 2024 (UTC)Reply[reply]

  •  Technically indistinguishable that 2022 jansin = SenvinCanvin2009 = 8348e = Demonx2018, but Inconclusive they are Jurisdrew. This is complicated by the use of proxies. {{Technically indistinguishable}} could also be the finding for several long-term, good-standing accounts that are clearly not Jurisdrew. Accordingly, the accounts named are those that also: 1) have subject matter overlap, 2) are relatively new, and 3) given their geographic location, would not be expected to be editing (for some, exclusively) United States flags. I do not say {{Possilikely}} or {{Likely}}, as I otherwise might as IPs do not overlap known Jurisdrew socks (which, again, may mean nothing due to proxies) and recent Jurisdrew socks have had tells which these do not. A thorough evaluation of behaviour needs to be the determinant. Эlcobbola talk 21:16, 21 January 2024 (UTC)Reply[reply]
✓ Done I blocked these accounts, and deleted the files. Yann (talk) 09:35, 23 January 2024 (UTC)Reply[reply]


KittenBroEeev (2)[edit]

Status: resolved • view • edit • history • watch
Filed: 14:56, 21 January 2024 (UTC)

Suspected related users[edit]

File:Vaymori (Ваймори) Tahriri1 Tahriri2.png - Link provided as a source is KittenBroEeev’s Pikabu account (linked in the previous request for checkuser), part of the "Tahriristan" nonsense. [3] [4]

Elmond[edit]

Status: open • view • edit • history • watch
Filed: 23:39, 19 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: m:Special:PermanentLink/26096094#Elmond@zh.wikipedia, I believe there are some sleepers hide here.Lemonaka (talk) 23:39, 19 January 2024 (UTC)Reply[reply]

  • Declined - All listed accounts are already confirmed at the link provided. There is thus no need for a redundant check of SUL accounts, and no evidence has been provided for "sleepers"-- Checkuser is not for fishing. Эlcobbola talk 01:14, 20 January 2024 (UTC)Reply[reply]
✓ Done All blocked. Yann (talk) 09:44, 23 January 2024 (UTC)Reply[reply]

AXXXXK[edit]

Status: resolved • view • edit • history • watch
Filed: 10:04, 19 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: See [5]. No edit anywhere except this. See previous RFCU. Yann (talk) 10:04, 19 January 2024 (UTC)Reply[reply]

I`m 99% sure it`s KittenBroEeev [6], [7] Kelly The Angel (talk) 11:49, 19 January 2024 (UTC)Reply[reply]
  • I didn't check, I followed Kelly's comment. Yann (talk) 23:01, 19 January 2024 (UTC)Reply[reply]
Sorry for the confusion. This user (KittenBroEeev) sometimes likes to engage in trolling and harassing other users, so I thought it might be him Kelly The Angel (talk) 03:28, 20 January 2024 (UTC)Reply[reply]


Alwataralwatar[edit]

Status: resolved • view • edit • history • watch
Filed: 19:40, 16 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploading the same type of images in terms of contents, in addition to similar usernames. It is noteworthy that the last account is blocked on Commons for "Uploading unfree files after warning" by Gbawden. Thanks on advance --Alaa :)..! 19:40, 16 January 2024 (UTC)Reply[reply]

 Comment This is so obvious that it doesn't need a CU. I reblocked the sock indef. Yann (talk) 19:59, 16 January 2024 (UTC)Reply[reply]

TCfanssos[edit]

Status: open • view • edit • history • watch
Filed: 18:10, 29 November 2023‎ (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Up to this point, Hatayjjv's sole purpose here was to repeatedly restore versions of maps uploaded by TCfanssos: [8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23] Aintabli (talk) 18:08, 13 January 2024 (UTC)Reply[reply]


Matlin[edit]

Status: resolved • view • edit • history • watch
Filed: 15:40, 11 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploaded bunch of uncategorized images from Daniel, in which Kukurydziarz (sock of Matlin) has also done so. A1Cafel (talk) 15:40, 11 January 2024 (UTC)Reply[reply]

  • Declined - Szczoch207 has already been blocked as a Matlin sock on wikidata by a CU there; there is no need for a redundant Commons check on an SUL account. Эlcobbola talk 15:46, 11 January 2024 (UTC)Reply[reply]


Jungan Pratama[edit]

Status:  to be archived • view • edit • history • watch
Filed: 08:53, 11 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: In the past several months, User:Jungan1104 has uploaded a number of copyrighted image (mainly logos) and was warned many times (see uploads log and user talk).

Four days ago, User:Jungan1104 was blocked 1 week for removed the file problems tag from a photo repeatly and other files (see COM:Administrators'_noticeboard/Vandalism#Jungan1104). A few hours later, the photo was re-created by User:Minnerbot XD and uploaded some images with the same interest ( TV logos).

Just now, I noticed this and tag with "Speedydelete". But User:Minnerbot XD suddenly warned me "Don't be careless in adding the Copyvio tag to free-to-use photos..." at my usertalk. User:Minnerbot XD then also made a similar accusation against me on user Juguan1104's usertalk and revert my edits on his uploads.

I strongly suspect that User:Jungan1104 is trying to use this puppet to get around the blocking and roll back my edits on his main account. 0x0a (talk) 08:53, 11 January 2024 (UTC)Reply[reply]

For older requests, please see Commons:Requests for checkuser/Archives
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Requests_for_checkuser&oldid=844371450"