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]

Momowearingmic[edit]

Status: open • view • edit • history • watch
Filed: 15:06, 2 June 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploaded the same copyrighted picture under multiple accounts (e.g., Special:Undelete/File:220722 TWICE Momo (4).jpg). I believe I've seen this copyright violation from other accounts before, so I'm asking for a sleeper check and possible IP block.

FWIW the master account is probably stale. Magog the Ogre (talk) (contribs) 15:06, 2 June 2024 (UTC)[reply]

POLITÍCO VINICIUS DE JESUS CRISTO[edit]

Status:  to be archived • view • edit • history • watch
Filed: 20:41, 20 May 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The name and upload were photos of the puppet master. All the best -- Chuck Talk 20:41, 20 May 2024 (UTC)[reply]

  •  No action - Obvious cases do not belong at RFCU ("Checkuser is a last resort for difficult cases; pursue other options first, such as posting on the administrator's noticeboard" (underline added)), and already confirmed 9. May on pt.wiki ("Requests to check accounts already confirmed on other projects may be declined as redundant"). Эlcobbola talk 20:56, 20 May 2024 (UTC)[reply]

Entersadmans[edit]

Status:  to be archived • view • edit • history • watch
Filed: 21:45, 14 May 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Preparation of single-use accounts, repeat offenders on other platforms. After reviewing each of the accounts, I noticed the same pattern of behavior which is to create an account, edit and abandon the account and if there are modifications where that account has been made, it intervenes again, repeating the cycle. Maroverse (talk) 21:45, 14 May 2024 (UTC)[reply]

I tend to decline this. No disruption at Commons has been shown. If it is a crosswiki issue, please report to stewards or please involve checkusers of mentioned other platforms. Krd 07:43, 18 May 2024 (UTC)[reply]

LIV2[edit]

Status:  to be archived • view • edit • history • watch
Filed: 23:00, 12 May 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason:trying to get File:Fancy pants logo for Wikipedia.png kept, and continuing to delete the DR template while the [[1]] DR is open. The IP continues the trend. All the best -- Chuck Talk 23:00, 12 May 2024 (UTC)[reply]

Theresadayog[edit]

Status:  to be archived • view • edit • history • watch
Filed: 16:06, 5 May 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Similar behaviour; uploading the exact same copyrighted image that was deleted twice when uploaded by sockmaster few days back. — Paper9oll (🔔 • 📝) 16:06, 5 May 2024 (UTC)[reply]

I also requested SPI on English Wikipedia, results (en:Wikipedia:Sockpuppet investigations/Theresadayog) came back that all are related to each other. I don't think any CU is required anymore on Commons hence may proceed to close this case. — Paper9oll (🔔 • 📝) 14:03, 6 May 2024 (UTC)[reply]
Given cross-wiki results, I have blocked and tagged all of these accounts. This case page may be archived now. ─ Aafī (talk) 14:44, 6 May 2024 (UTC)[reply]

E333ter[edit]

Status:  to be archived • view • edit • history • watch
Filed: 06:25, 5 May 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The former user, who is globally locked, posted in Russian Wikipedia an image used only for vandalism which was uploaded by the latter. Тай Лунг (talk) 06:25, 5 May 2024 (UTC)[reply]

And the latter is to be globally locked as well as the former. 185.10.224.66 06:30, 5 May 2024 (UTC)[reply]
@Тай Лунг: both now locked, this request is now moot.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 13:49, 5 May 2024 (UTC)[reply]
  •  Not done - Noting for posterity and clarity in case of future requests, as already marked as resolved. Indeed, as per above, both accounts globally locked (E333ter as of, and Gtefer less than 13 minutes after, this request), so no CU needed to prevent disruption. Эlcobbola talk 16:24, 12 May 2024 (UTC)[reply]

A3cb1[edit]

Status:  to be archived • view • edit • history • watch
Filed: 21:45, 7 May 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Same edit pattern as previous socks. 81.41.177.91 21:46, 7 May 2024 (UTC)[reply]

✓ Done --Krd 05:24, 9 May 2024 (UTC)[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=880846983"