Last modified on 21 May 2015, at 23:35

Commons:Requests for checkuser

Shortcut: COM:CHECK, COM:RFCU

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

David BealsEdit

Suspected related usersEdit

RationaleEdit

  • the usual image loaded over medium to high use images. Please check for sleepers and get this account locked. --Denniss (talk) 08:10, 17 May 2015 (UTC)
    • Two new suspected socks added, getting back to the old QR-code spam. Please check for sleepers and get accounts locked.--Denniss (talk) 13:34, 21 May 2015 (UTC)

ResultsEdit

Artículo bueno.svg Confirmed, no sleepers found. --Krd 08:27, 17 May 2015 (UTC)

Artículo bueno.svg Confirmed, two more likely socks blocked. --Krd 13:46, 21 May 2015 (UTC)
I've been running checks on a bunch of his accounts on the English Wikipedia an blocking them. I'll look at some cross-wiki contributions and run some sleeper checks here. Tiptoety talk 04:32, 22 May 2015 (UTC)


Il macio88Edit

Suspected related usersEdit

RationaleEdit

Reason: Same range of contribution of A3cb1, banned indefinetly for violation of copyright and abuse of multiple accounts.--Caarl 95 (talk) 13:02, 20 May 2015 (UTC)

ResultsEdit

Artículo bueno.svg Confirmed and blocked. --Krd 07:42, 21 May 2015 (UTC)


VS6507Edit

Suspected related usersEdit


RationaleEdit

  • VS6507 recently uploaded a map that he claimed was "own work", but seems to be copied from here. So, I started Commons:Deletion requests/File:2014 Serbian Parliamentary Elections Majority Map.jpg. These two IP addresses suddenly appeared in the deletion discussion, arguing that the image should be kept, for the same (bizarre) reason that VS6507 gave; these IP addresses have never edited any other Commons page; VS6507 has been blocked for sockpuppetry, copyright violations, and vote-stacking on Commons and several other wikis in the past (much of the evidence predates VS6507's recent change of account name). [1] [2] [3] [4] [5] [6] [7] etc.
  • @Denniss: already blocked one of the IPs, as a proxy. I am not very worried about the other IP - future abuse of that IP would be obvious - but I would invite an administrator to consider whether it is reasonable to reinstate @Tiptoety:'s indefinite block of VS6507. bobrayner (talk) 23:20, 21 May 2015 (UTC)

ResultsEdit

  • Per a discussion amongst checkusers, this is best considered Symbol unsupport vote.svg Inconclusive. Please feel free to block based on behavior and considerations of {{duck}}. Эlcobbola talk 19:19, 24 May 2015 (UTC)
Is that due to the IPs being proxies? Since VS6507 was last unblocked, there have been other cases where proxies made edits to advance VS6507's cause, such as [8] and [9]. bobrayner (talk) 23:42, 24 May 2015 (UTC)

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