Commons:Requests for checkuser

Shortcut: COM:CHECK, COM:RFCU, COM:SOCK

Does your request belong here?
This is the place to request sockpuppet checks or other investigations requiring CheckUser privileges. Checkuser is a last resort for difficult cases. Use other methods first. You can try posting on the administrator's noticeboard for example.
Please do not ask us to run checks without good reason:
These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments.
Request completed
Artículo bueno.svg Confirmed Likely
Symbol possible vote.svg Possible Symbol unlikely.svg Unlikely
Symbol unsupport vote.svg Inconclusive Symbol unrelated.svg Unrelated
Symbol redirect vote.svg Completed Time2wait.svg Stale
Request declined
Declined Checkuser is not for fishing.
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
Cyberduck icon.png It looks like a duck to me Checkuser is not a crystal ball.
Information
Additional information needed Deferred to
 Doing… Pictogram voting info.svg Info
  1. 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 vandalism where a block of the underlying IP or IP range is needed, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption to Wikimedia projects.
  2. Requests to run a check with ambiguous reasoning will result in delays - please provide a rationale at the time you make the request
    • Show what the disruption to the project is, and why you believe the accounts are related.
  3. Requests to run a check on yourself will be declined
  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. Check back regularly to see the outcome of your request. Closed requests are archived after seven days.
Privacy violation?
If you feel that a checkuser has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombudsman 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 (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.

RequestsEdit

ArtWriter1Edit

Suspected related usersEdit

Rationale, discussion and resultsEdit

Reason: Reupload of the same image: File:Green-T-Stratocaster-Guitar-Ed-Sheeran-Teddy-M.jpg and File:Green-T-by-Teddy-M-played-by-Ed-Sheeran-2015.jpg. Uploads claimed as "own works", which can't be true: File:Teddy-M-Range-Rover-Art-Car-2017-installation-wrapstyle.jpg is obviously a selfie by Teddy M. See also en:Teddy M. Yann (talk) 21:42, 22 March 2017 (UTC)

  • It seems plausible to me this is a case of forgotten username/password, rather than necessarily malicious sockpuppetry. It also seems plausible that the uploader is in fact Teddy M.
  • From a CU standpoint, I would ask you to consider if you still think this is necessary. Magog the Ogre (talk) (contribs) 04:20, 23 March 2017 (UTC)

Team.workEdit

Suspected related usersEdit

Rationale, discussion and resultsEdit

Reason: Team.work is undefinitely blocked by Magog. Bob.mob (File:Moroccan ID for edit.jpg) and Habib Allah dhmani (File:الهوية.jpeg) both reuploaded an image uploaded by Team.work, and deleted as copyright violation: File:Morroco ID.jpg. No useful edit for any of the account so far. Yann (talk) 21:25, 22 March 2017 (UTC)

  Likely. Both blocked. --Krd 21:36, 22 March 2017 (UTC)

Kritkitty again and again and again and againEdit

Suspected related usersEdit


Rationale, discussion and resultsEdit

Behaviour consistent with previous sockpuppets, e.g. this file log. Uploaded files are edited from an IP address in Thailand shortly after upload (listed above). LX (talk, contribs) 13:56, 18 March 2017 (UTC)

Krd: Just want to bring this to your attention, as I believe the data on the last known sockpuppet, Myan-bruma8888 (talk contribs Luxo's SUL deleted contribs logs block user block log checkuser), is about to expire. LX (talk, contribs) 07:05, 21 March 2017 (UTC)
  Confirmed and blocked. --Krd 17:46, 22 March 2017 (UTC)




SviramanEdit

Suspected related usersEdit

Rationale, discussion and resultsEdit

Reason: They are obviously not new and uploading files with improbable own work claims. Please check whether this is one of our long time abusers. Jcb (talk) 17:25, 15 March 2017 (UTC)

  Oppose Check user is not for fishing. Yann (talk) 09:46, 18 March 2017 (UTC)
This is not fishing. This is an obvious sockpuppet (you are experienced enough to know that), so it seems plausible to me that a checkuser has a look to see if this is one of our long time abusers. Jcb (talk) 21:58, 18 March 2017 (UTC)

  Checkuser is not for fishing. With all due respect to Jcb, I see nothing improbable about the copyright claims, nor any support to the assertion that this may be someone violating COM:SOCK. If you would like to pursue this further, please provide more evidence. Magog the Ogre (talk) (contribs) 03:38, 23 March 2017 (UTC)

TarchivumEdit

Suspected related usersEdit

Rationale, discussion and resultsEdit

Reason: Same behaviour: both work almost exclusively on the history of Vietnam, with (presumably) good work being done, but they keep adding new categories whilst overwriting older, relevant ones (see for instance [1], [2], [3], [4]). Mere clumsiness is rather unlikely as Tachivum otherwise shows good command of wiki editing, like adding categoryTOC to a category. Account Tarchivum was created the day after Unserefahne was blocked for a week by Jcb for "disruptive editing after multiple warnings". This disruptive behaviour includes the above mentioned disruptive category editing (warnings from Daderot and myself), uploading copyvios, deleting problem tags from files (warnings from Jcb and Yann) and insulting Daderot. As a note, Unserefahne is blocked indefinitely on en: for evading their block by using a sockpuppet. Jastrow (Λέγετε) 10:02, 16 March 2017 (UTC)

  Confirmed. Blocked Tarchivum indef and Unserefahne for 1 month from now. --Krd 08:19, 18 March 2017 (UTC)

Note: the same user seems to be back in action, now with user name Btarchiv (talk contribs Luxo's SUL deleted contribs logs block user block log checkuser). cheers, Daderot (talk) 12:48, 20 March 2017 (UTC)

I concur. I have taken the initiative of blocking this "new" user for 3 days because I'm fed up of reverting them (disruptive editing now includes changing licences). Do I have to open a new request about Btarchiv (talk · contribs)? Jastrow (Λέγετε) 08:31, 22 March 2017 (UTC)
  Possible. Blocked indef. --Krd 17:42, 22 March 2017 (UTC)

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