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]

Guishín Pastofrio

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: AcutÁngulo was registered today to upload images of Uruguayan politicians, the same topic of interest as Guishín Pastofrio, but at the same time it is on Spanish Wikipedia restoring controversial edits of the same subject. It is very possible that it is a DUCK but I want clear confirmation of the situation. Taichi (talk) 00:56, 21 December 2024 (UTC)[reply]

Possible --Krd 07:12, 21 December 2024 (UTC)[reply]

Auntitis

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Accounts created the same day, and uploading the same deleted content: File:Oinarri aniztun blokea.webp and File:Oinarri aniztun blokeak.png. Yann (talk) 16:20, 19 December 2024 (UTC)[reply]

Likely --Krd 05:26, 20 December 2024 (UTC)[reply]

Tamillifehacking

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: DhayanidhiSK reuploaded deleted files previously uploaded by globally locked account Tamillifehacking. Yann (talk) 11:44, 19 December 2024 (UTC)[reply]

Confirmed --Krd 12:17, 19 December 2024 (UTC)[reply]

Ricardinho da Souza Silva 7

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Once again another duck. Banking edits have started both in Commons and eswiki. --Stïnger (会話) 04:52, 20 December 2024 (UTC).[reply]

Inconclusive --Krd 05:28, 20 December 2024 (UTC)[reply]

Ricardinho da Souza Silva 7

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Another duck. Massive banking-related edits in Commons, extending to eswiki and enwiki as well. --Stïnger (会話) 13:29, 13 December 2024 (UTC).[reply]

Confirmed --Krd 05:47, 14 December 2024 (UTC)[reply]

Loveisamoracle

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Context: a few weeks ago there was an election in UY. For the benefit of the doubt, these three accounts could be just activists colliding in their editions, because they have a strong ideological and partisan bond. Maybe, they just have some kind of coordinated effort, and nothing else.

But the three of them uploaded several images taken from the internet in copyright violation, even through license laundering (via Flickr). As you may see in their User talks, a lot of images were already deleted, and two of this three accounts were blocked here, one of them indefinitely. They insisted in trying to include these images in SP:WP showing the same behavior: edit wars, incivility and sarcastic remarks, ignoring warnings sistematically, etc. Two of them were already blocked on SP:WP.

The problem here in Commons is what you see in their User Talks, as said above. Is it a case of multiplle accounts or just false alarm? Loveisamoracle is the older one by far, the other two were created a year ago, more or less.--Rastamby (talk) 05:31, 13 December 2024 (UTC)[reply]

This is technically Inconclusive or a weak Possible. --Krd 08:34, 13 December 2024 (UTC)[reply]

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