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]

F. Tales Massei[edit]

Status: open • view • edit • history • watch
Filed: 00:01, 14 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: I'm pretty sure these three accounts are socks of F. Tales Massei (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information). They all uploaded pictures of Massei or related to him. Histórias Puritanas (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) tried to create and recreated and article for him in the pt.WP. Kacamata! Dimmi!!! 00:01, 14 December 2023 (UTC)Reply[reply]

+L Oai iu aahhaahh[edit]

Status: open • view • edit • history • watch
Filed: 23:13, 13 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Another suspect per this edit.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 23:13, 13 December 2023 (UTC)Reply[reply]

  • Finsoja2 has never edited the Commons, or any other project. Creation was February 2023, so even attachment would be Stale. Эlcobbola talk 23:20, 13 December 2023 (UTC)Reply[reply]

Adv Sh Mishra[edit]

Status: open • view • edit • history • watch
Filed: 12:29, 12 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Crosswiki spam. The master uploaded a few selfies and wrote a preliminary autobiography at his user page (now blanked and tagged G10), then a more comprehensive one at en:Draft:Adv Sh Mishra (now deleted}. The puppet then uploaded another selfie and tried to repeat the autobiography at the master's user page and complained about hitting Special:AbuseFilter/245 and Special:AbuseFilter/186 in COM:FILTERT#Report by Ansh2512 using these edits.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 12:29, 12 December 2023 (UTC)Reply[reply]

Matteo sportelli[edit]

Status: resolved • view • edit • history • watch
Filed: 02:18, 11 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Similar username pattern + reuploading Special:Undelete/File:Empire State Building 1,454 ft.jpg as Special:Undelete/File:Empire State Building 1454 ft.jpg. —‍Mdaniels5757 (talk • contribs) 02:18, 11 December 2023 (UTC)Reply[reply]


Cuken26111[edit]

Status: resolved • view • edit • history • watch
Filed: 11:40, 9 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploading drawings by living Chinese artist. The user had previously created multiple sockpuppet accounts to circumvent blocking. See COM:Administrators' noticeboard/Blocks and protections#User:Cuken2613. 0x0a (talk) 11:40, 9 December 2023 (UTC)Reply[reply]

  • Declined - Per COM:EVID: "Evidence is required. When you request a check, you must include a rationale that demonstrates (e.g., by including diffs) [...] why you believe the accounts are related." (underline in original) "Uploading drawings by living Chinese artist" is entirely inadequate. Are we meant to believe that every account uploading the work of a living Chinese author is related? Are Shizhao and Mys 721tx the same person? If you desire a check, actual evidence of a connection needs to be provided; it is not the job of checkusers to build cases for you. Эlcobbola talk 16:13, 9 December 2023 (UTC)Reply[reply]
    I can't find a direct connection between the two accounts. But, these two files, Trụ Vương.png and Mai Bá.png, were re-uploaded by the same account on the same day. Can we infer that User:Hcjks12 and User:Muzarc1098 are the same user? 0x0a (talk) 17:06, 9 December 2023 (UTC)Reply[reply]
    Thank you, that is all that was needed. Confirmed, with many others. Эlcobbola talk 17:39, 9 December 2023 (UTC)Reply[reply]

HassanGX820[edit]

Status: resolved • view • edit • history • watch
Filed: 02:03, 6 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Reuploaded Special:Undelete/File:Hassan of Morocco.jpg as Special:Undelete/File:Mulay Hassan.jpg. —‍Mdaniels5757 (talk • contribs) 02:03, 6 December 2023 (UTC)Reply[reply]

Takiva[edit]

Status: resolved • view • edit • history • watch
Filed: 11:04, 3 December 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: This account makes very similar edits to Takiva, and is primarily interested in files relating to maps and flags of Algeria's history. The account has also edited files which Takiva (and their sockpuppets) originally created or edited, such as Flag map of Chaouia, Flag-map of Algeria and Flag map of the Almoravid dynasty. Skitash (talk) 11:04, 3 December 2023 (UTC)Reply[reply]

Confirmed --Krd 11:15, 3 December 2023 (UTC)Reply[reply]

Matlin[edit]

Status: resolved • view • edit • history • watch
Filed: 07:44, 30 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Opened a DR on FoP issue, in which Matlin has done so previously. Also, The Fourth Zone was blocked on Wikidata per behaviour, but IMO just one DR is not enough to justify a duck test. A1Cafel (talk) 07:44, 30 November 2023 (UTC)Reply[reply]

Matlin[edit]

Status: resolved • view • edit • history • watch
Filed: 10:29, 19 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploading lots of Flickr files without categorization. Matlin was blocked multiple times in 2021-2022 for mass-upload without proper categorization, Kukurydziarz seems created to avoid scrutiny and evade the blocks on using the F2C tool. Account was blocked on Wikidata as socks of Matlin, but there is not obvious enough to be directly blocked. Therefore, a check is required. A1Cafel (talk) 10:29, 19 November 2023 (UTC)Reply[reply]

To expand upon the above, the block on WikiData was for possible block evasion. A1Cafel had requested a block at COM:ANB, but I had felt a bit uncomfortable with blocking here on the sole basis of that edit summary. I think that it may well warrant a check here if there's a pattern of similar behavior (which A1Cafel notes above) while also having a large sister wiki blocking Kukurydziarz as a possible sock of Matlin. The use of multiple accounts to evade a restriction on using the Flickr2Commons tool would be a cause for blocking the user. The usefulness of a check here would be to better establish whether or not these two accounts are technically connected. — Red-tailed hawk (nest) 04:53, 20 November 2023 (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=830443652"