Commons:Requests for checkuser

From Wikimedia Commons, the free media repository
Jump to: navigation, search

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.

Requests[edit]


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

Ethan Doyle White[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: While categorizing photos of British monuments, I came across photos by two different uploaders who are almost certainly using photos by the same photographer. As an example, see the camera metadata for File:Julliberrie's Grave in September 2012.jpg by Ethan Doyle White and File:Julliberrie's Grave 2.jpg by Midnightblueowl. These photos were taken at the same site, 12 minutes apart, using the same model camera (an HTC Rhyme S510b). Earlier, both users have submitted photos from a Casio EX-V7 - see File:Woodhenge, Wiltshire.JPG and File:Stonehenge Winter Solstice 2011.jpg. If these are in fact different users, then one of them is using the other's photos without permission. Kelly (talk) 19:54, 1 October 2016 (UTC)

  • It's usually necessary for there to be disruption to warrant a checkuser. Commons:Sockpuppetry links to the Wikipedia page, which lists several legitimate uses for alternate accounts. I don't see disruption by this user on Commons. Magog the Ogre (talk) (contribs) 02:38, 2 October 2016 (UTC)
    • @Magog the Ogre: OK, thank you. ArbCom at en is looking at the issue anyway and we can sort out the copyright implications for all the photos later. Kelly (talk) 08:37, 2 October 2016 (UTC)
  • Declined per above. Magog the Ogre (talk) (contribs) 13:56, 2 October 2016 (UTC)

Alex9777[edit]

Suspected related users[edit]

older accounts I added on the fly to newly created Category:Sockpuppets of Alex9777 some of which haven't been checked or blocked by now:

found more:

--Achim (talk) 05:47, 10 September 2016 (UTC)

Rationale, discussion and results[edit]

Reason: Sock farm of a self-promoting "famous blogger", see also en:Wikipedia:Sockpuppet investigations/Alex9777777. --Achim (talk) 13:20, 7 September 2016 (UTC)

File link spam[edit]

Rationale, discussion and results[edit]

Reason: @Herbythyme: alerted me to a series of url spam that is being secreted into flickr uploads. The behaviour looks to have been taking place for at least 9 months, though there seems to be a reasonable amount recently. It would be useful to see if there is a pattern in the IP addresses and the ability to either single or range IP block the problematic editor. There is some stuff that can be done for bot management however, it looks to be paid spam with a person slow-feeding it through uploadwizard with a plethora of urls being added.

There will be plenty more at a guess, this is pretty insidious.  — billinghurst sDrewth 13:53, 4 September 2016 (UTC)

There's a real lot of stuff, so it will take some time to sort it. Definitely not to be resolved by single IP/range blocks. --Krd 14:14, 4 September 2016 (UTC)

Here are some more blocked. I have now stopped digging for blocks, and just removing the spam.

 — billinghurst sDrewth 14:23, 4 September 2016 (UTC)

Added for re-check:

--Krd 14:33, 4 September 2016 (UTC)

Slightly different story:

--Krd 16:06, 4 September 2016 (UTC)

All done for the moment, although I have some feeling there could be even more. Please report further occurrences! --Krd 18:29, 4 September 2016 (UTC)

Pinging Krd: For the records, seems to be continuation of Commons:Requests for checkuser/Case/Cjones934. --Achim (talk) 21:18, 8 September 2016 (UTC)
I knew I had seen this before, but I didn't find the actual case. Thank you!
I suggest to keep this open for a while and gather additional suspects here. --Krd 06:01, 9 September 2016 (UTC)
You're welcome. Here we go:
Gruß, --Achim (talk) 09:50, 9 September 2016 (UTC)
--Achim (talk) 15:08, 9 September 2016 (UTC)

 — billinghurst sDrewth 06:13, 10 September 2016 (UTC)

Krd. I am seeing a couple of the domains being spammed turning up in articles at enWP, so it might be worth alerting the checkusers there to data and some of your IPs if you are seeing some trends. For example article w:Everlake.  — billinghurst sDrewth 07:01, 10 September 2016 (UTC)
I'm going to leave for vacation today, so I'm unable to push this further for the next two weeks. That data gathered here is documented at the usual place, so enwiki CUs can take a look. If you have a moment to ping them, please go ahead. --Krd 07:09, 10 September 2016 (UTC)
BTW, the amount of accounts and files affected here is amazing. I'm already working on a more general solution, but this will take some time to implement. Until then, please feel free to collect data here. I'm going to check this as soon as I'm back online. --Krd 07:11, 10 September 2016 (UTC)
Not shure whether or not it belongs to this case, I noticed that 3 of the promoted domains shew up recently on direct ads:
Best, --Achim (talk) 07:50, 10 September 2016 (UTC)
Thanks for those. I have cleaned up.  — billinghurst sDrewth 08:01, 10 September 2016 (UTC)
@Mike V, DoRD, Materialscientist: please note the above conversation which may have repercussions at enWP.  — billinghurst sDrewth 07:56, 10 September 2016 (UTC)

┌─────────────────────────────────┘

--Achim (talk) 20:04, 10 September 2016 (UTC)

October 2016[edit]

@Krd: the spam continues

Earlier block without enWP link, think that there will be more around this time

 — billinghurst sDrewth 07:50, 2 October 2016 (UTC)

 — billinghurst sDrewth 13:20, 2 October 2016 (UTC)

Will look into at Tuesday evening. --Krd 16:39, 2 October 2016 (UTC)

Anitnovic2016[edit]

Suspected related users[edit]


Rationale, discussion and results[edit]

User:Anitnovic2016 is a sock of User:KatorseNiAmang and have been using the above mentioned IP to remove deletion tags from their uploads that appears to be copyvios. See 1, 2, 3. This history sum it up. For the record, w:User:KatorseNiAmang has been confirmed as a sock puppet of w:User:Anitnovic2016 on the English Wikipedia. Wikicology (talk) 15:42, 4 September 2016 (UTC)

Just to clarify, en:User:KatorseNiAmang and en:User:Anitnovic2016 were determined to be sockpuppets of en:User:Ronald Galope Barniso, who was indefinitely blocked on English Wikipedia for threatening other editors among other things. -- Marchjuly (talk) 01:52, 5 September 2016 (UTC)