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]

Aliphotography

[edit]

Reason: ArionStar was blocked for 12 months (see Special:PermaLink/936836772#ArionStar) and indefinitely banned from COM:FPC due to repeated disruptive editing on 10:15, October 10, 2024 by Yann. Talk page access removed on December, 13, 2024 (see here) by The Squirrel Conspiracy.

  1. The day after, immediately, this brand new account is created.
  2. This discussion gives several clues that different users have to suspect this account is a sockpuppet. Same behavior (only interest in nominations at FPC, poor discernment of valid candidates)
  3. Brazil oriented nominations, 2,
  4. Similar smileys to old signature,
  5. Global account linked to portuguese-WP,
  6. Same kind of disruption as in the past,
  7. IP located in a place where ArionStar uploaded pictures,
  8. Low discernment of FP-value like before,
  9. Messing up infos in upload section.
  10. Heavy rush and disruption by adding pictures not yet promoted, and removing fair FP from the gallery, exactly like ArionStar did in the past (example FP categories added only 2 days after the nomination.

-- Basile Morin (talk) 04:19, 30 December 2024 (UTC)[reply]

If you are creating a new request about this user, please add it to the top of the page, above this notice. Don't forget to add
{{Commons:Requests for checkuser}}
to the checkuser page here. Previous requests (shown below), and this box, will be automatically hidden on Requests for checkuser (but will still appear here).
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.

ArionStar

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: ArionStar was just blocked for 12 months (see Special:PermaLink/936836772#ArionStar) and indefinitely banned from FPC due to repeated disruptive editing on 10:15, October 10, 2024 by Yann. This new account was created on 10:53, October 10, 2024 and their very second edit happens to be a delist nomination (though with much better English than ArionStar's). The timing of it seems far to coincidental, hence the CU request. --SHB2000 (talk) 12:03, 10 October 2024 (UTC)[reply]

Unlikely Krd 12:08, 10 October 2024 (UTC)[reply]
Actually, I don't think this is ArionStar. I agree with the assessments by Cmao20 here, but I can't believe this is a new user. Yann (talk) 12:33, 10 October 2024 (UTC)[reply]
The same here. I cannot imagine that RealPhotoManiac is ArionStar (the new user seems to know much about technical fine points of photography, that’s definitely not Arion’s cup of tea), but I also doubt that this is a new user – they seem to be very familiar with typical FPC discussions etc. Would it be possible to do a more general checkuser, I mean, to check whether RealPhotoManiac is a new incarnation of some other banned Commons user? The most probable candidates are certainly banned users who (1) know much about photography and (2) were regular contributors to the FPC page. I imagine that doing a comparison of the list of banned users with the users in our FP statistics would yield some good candidates to be checked; people like User:PumpkinSky … Just my 50 cent, – Aristeas (talk) 13:23, 10 October 2024 (UTC)[reply]
The above discussion is preserved as an archive of the Request for checkuser. Please do not modify it.
Subsequent requests related to this user should be made
above, in a new section.


Achitphon

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Both users were created in the same week (15 and 22 November), they have similar names, and what they the core of my suspicion they both upload the same copyvios using the same "particular" name convention, see for example File:MCB2023.jpg and File:MCB2016.jpg. Anolphat is currently blocked for 2 weeks for uploading copyvios. Günther Frager (talk) 13:34, 28 December 2024 (UTC)[reply]

 Comment I blocked Achitphon as obvious sockpuppet, and reblocked Anolphat indef. as Achitphon is actually the oldest account. Nothing useful. It would be useful to know if there are dormant accounts. Yann (talk) 13:53, 28 December 2024 (UTC)[reply]
Confirmed --Krd 17:39, 28 December 2024 (UTC)[reply]

الساحرالسفلي امير الصابئي ساحر الكهوف

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: upload violation photos.  Mohammed Qays  🗣 12:29, 28 December 2024 (UTC)[reply]

Confirmed --Krd 17:43, 28 December 2024 (UTC)[reply]

Vijaysvijay

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Reuploading File:Freedom Fighter Ramesh Chandra Jha.jpg/File:Ramesh Chandra Jha.jpg, but with enough differences in the file page that I'd prefer to have some technical evidence before blocking. Also seem to share an interest in Dhruva Kumar. —‍Mdaniels5757 (talk • contribs) 04:30, 27 December 2024 (UTC)[reply]

Confirmed --Krd 07:20, 27 December 2024 (UTC)[reply]

ابن عرب العمريه العمري

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason:He returned after blocking his account to upload violation photos.  Mohammed Qays  🗣 11:56, 22 December 2024 (UTC)[reply]

Confirmed --Krd 12:08, 22 December 2024 (UTC)[reply]
Please block this account: هزاع الظواهره العمري (talk contribs Luxo's SUL deleted contribs logs block user block log )  Mohammed Qays  🗣 17:21, 23 December 2024 (UTC)[reply]
@Krd  Mohammed Qays  🗣 17:21, 23 December 2024 (UTC)[reply]
✓ Done --Krd 06:32, 24 December 2024 (UTC)[reply]

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