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]

Sharikkhanjr

[edit]

Status: resolved • view • edit • history • watch
Filed: 14:04, 20 June 2024 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: reuploading same out of scope personal images from multiple accounts after being warned so many times Waqar💬 14:04, 20 June 2024 (UTC)[reply]

REDƎYE

[edit]

Status: resolved • view • edit • history • watch
Filed: 23:19, 18 June 2024 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Over the last few weeks, several admins both here and on Wikidata have been working to clear out hundreds of unnecessary categories and corresponding Wikidata items created by REDƎYE to promote his BoOzy’ OS media franchise, which both en.wiki and fr.wiki have determined to be not notable. As originally pointed out by William Graham (talk · contribs) on my Wikidata talk page, the WikiSyn account was involved in creating BoOzy’ OS categories as well, prior to the REDƎYE account. The REDƎYE user page claims that it and WikiSyn are not the same person, they just occasionally share the same IP, but based on the content they created (which is narrow in scope and heavily overlaps), it's reasonable to assume that both are accounts operated by J.K. Arsyn, the creator of BoOzy’ OS. Streets4rage has an editing overlap with WikiSyn in both BoOzy’ OS and Sega content, and the account became active after half a year of no edits on any project to make their first edits on Commons in Commons:Deletion requests/Files uploaded by REDƎYE. To me, both that Commons DR and en:Wikipedia:Articles for deletion/BoOzy' OS and the Cristal Gem are very transparently the subject of either sockpuppetry or meatpuppetry. The Squirrel Conspiracy (talk) 23:19, 18 June 2024 (UTC)[reply]

Hello, please read my comments here.
Sincerely yours, - ʂɤɲ ✉ 06:02, 19 June 2024 (UTC)[reply]
  • I'm inclined to decline this. Both REDƎYE and WikiSyn acknowledge a relationship, so there is nothing to be learned from a CU (a hypothetical finding of confirmed would only tell us what we already know--they are related). Regarding Streets4rage, adequate evidence has not been provided; while this deficiency could likely be remedied, I'm not convinced that their two edits rise to the level of "a last resort for difficult cases". I'll leave this open in case another CU sees things differently, but I would suggest blocking REDƎYE as a COM:IU violation ("Use of the names of organizations is allowed on Commons only if you verify your account, proving that you are or represent the respective organization" (bold added) - see REDƎYE pictures) and warning Streets4rage (and filing a new CU if that account again appears to double-vote or otherwise abuse multiple account). WikiSyn was stale when this request was made, so they appear only to have become active to address this CU. Эlcobbola talk 14:07, 20 June 2024 (UTC)[reply]

Franklin482

[edit]

Status: open • view • edit • history • watch
Filed: 13:13, 17 June 2024 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Vandalism, hoaxing, changing upload logs on some files reserved as templates, uploading copyvio and duplicate content, creating random road signs and categories for highways that don't exist, and (partially) blocked on Wikimedia Commons and English Wikipedia for that behavior. Users have similar contributions since 2018. The person admitted here that has created several accounts. Yarfpr (talk) 13:06, 17 June 2024 (UTC)[reply]

 Comment I blocked Franklin482 and Harrison Canyon. They are probably stalled, but edits and uploads create little doubt about socking. They are proved socks of one another on enwiki. Yann (talk) 11:45, 18 June 2024 (UTC)[reply]

Jason ihsas

[edit]

Status: open • view • edit • history • watch
Filed: 22:25, 13 June 2024 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Uploading the same copyvio content. Ankry (talk) 22:25, 13 June 2024 (UTC)[reply]

Inconclusive Krd 07:24, 14 June 2024 (UTC)[reply]
✓ Done Blocked, as obvious sock. Yann (talk) 11:38, 18 June 2024 (UTC)[reply]

Jesus-rojas 232

[edit]

Status: open • view • edit • history • watch
Filed: 14:41, 5 June 2024 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Apart from the similarities with the names, all these user upload and recreate deleted logos of Carrefour. Checking Commons:Deletion requests/Files in Category:Logos of Carrefour Group and Commons:Deletion requests/Files in Category:Carrefour one can see that almost all files were uploaded by one of these users. Günther Frager (talk) 14:41, 5 June 2024 (UTC)[reply]

  • Despite being an obvious {{Duck}} case that would otherwise be declined for that reason, I've run the check because there are many, many other obvious accounts not listed (e.g., Jesus rojas 435, Jesus-Rojas-1997, Jesus-Rojas-966, Jesus Rojas-763, Jesus Rojas-766, Jesus Rojas-767) over an extended period of time to identify 1) additional non-stale sleepers and 2) possible range blocks. Of those in the request: Jesús-rojas432 and Jesus Rojas995 are Stale (but  It looks like a duck to me), others listed are Confirmed, among others. Эlcobbola talk 15:48, 5 June 2024 (UTC)[reply]
✓ Done I deleted all files and categories. Yann (talk) 14:53, 20 June 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=885766918"