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

Wunnakyaw1Edit

Suspected related usersEdit

See Category:Sockpuppets of Wunnakyaw1.

Rationale, discussion and resultsEdit

Reason: This is related to Commons:Administrators' noticeboard#Influx of files with embedded data .28CSD.23F9.29. In the category above are all suspected sockpuppets of a user uploading sometimes very big files, disguised as an image. It's starting to get out of hand with about one new user and upload per hour. The uploaded "cover" files are a variety of different files, but everything points to south-east Asia. Sebari – aka Srittau (talk) 10:57, 30 November 2016 (UTC)

Over 100 suspected sockpuppets by now. --Sebari – aka Srittau (talk) 14:47, 1 December 2016 (UTC)
Apparently the listed socks are already blocked on behaviour, and efforts are taken to detect the given abuse in general. Please advise what is expected from this CU request? --Krd 06:20, 5 December 2016 (UTC)

For older requests, please see Commons:Requests for checkuser/Archives
https://commons.m.wikimedia.org/wiki/Commons:Requests_for_checkuser
commons.m.wikimedia.org
crawl=CC-MAIN-2016-50
34430
application/http; msgtype=response
sha1:6XMDY7XFZTKZKWRJ4GQPUKZRLN6LXK3I
<urn:uuid:daeface8-a762-49cf-8990-e15b5389af8e>
2016-12-05T09:21:24Z
208.80.154.224
sha1:VJ7XVAFDAWVDJMA3IJYX7NU6XRME2Y7Y
<urn:uuid:dece0e09-2218-4b29-907d-5207921b99d2>
https://commons.m.wikimedia.org/wiki/Commons:Requests_for_checkuser
length
response
<urn:uuid:89ff136a-6f05-419d-b6cb-21d3825e78f0>
robots: classic
hostname: ip-10-31-129-80.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2016-50
operator: CommonCrawl Admin
description: Wide crawl of the web for November 2016
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf