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.

Checkuser requests to be listed‎ (empty)
nothing found

Requests[edit]

Dnazf[edit]

Status: resolved • view • edit • history • watch
Filed: 04:11, 1 February 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The master account (Dnazf has limited contributions to Commons, but still manages to have several files deleted for copyright/licensing issues. Among these is Ergene nehri.jpg, which was uploaded while editing "Ergene" on tr.wikipedia.org. After the first file was deleted for licensing reasons, the sockpuppet (Tarkyldz re-uploaded the same file, but under a different name (File:Ergene.jpg).

Both the master and sock have contributions only to the Turkish Wikipedia and Commons. Among the 4 undeleted contributions of the master to the Turkish Wikipedia, one of them was to add the image in question to the "Ergene" article. The sockpuppet also has relatively few contributions on TrWiki, but several of them also added the same image (under the name of the re-upload) to the infobox of the "Ergene" article there.

For the above reasons, I suspect that there may be some connection between the two accounts. As such, I am requesting a CheckUser investigate whether a technical connection between the two exists. If connected, the use of the second account to re-upload a deleted image that the first account had already attempted to place on Commons would appear to evade scrutiny as to the account holder's compliance with the licensing policy.

— Red-tailed hawk (nest) 04:11, 1 February 2024 (UTC)Reply[reply]

Giorgio Pallavicini[edit]

Status: resolved • view • edit • history • watch
Filed: 20:51, 31 January 2024 (UTC)


Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Giorgio Pallavicini has been blocked on March 5th, 2023, because of massive overwriting of photos of portraits paintings and old portraits photos with "enhanced" versions obtained via AI. I've recently noticed that Giorgio Pallacivini, on the Italian Wikipedia (we are both Italian), is now changing in many biographies of aristocrats the main picture, substituting it with an AI "enhanced" version. All these pictures have been uploaded here by user Fecefece. This last one is blocked on the Italian Wikipedia as a sockpuppet, but apparently the admin forgot to put the template linking that profile to Giorgio Pallavicini (so there is not officially a prove that they are the same person). Just for the info, I was discussing about that topic with another user here on Commons, and Giorgio Pallavicini replied without login (but he signed).--Kaho Mitsuki (Dis-moi) 20:51, 31 January 2024 (UTC)Reply[reply]

Inconclusive --Krd 09:00, 1 February 2024 (UTC)Reply[reply]

Instant Edge[edit]

Status: resolved • view • edit • history • watch
Filed: 21:55, 28 January 2024 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Repeat spammer. See upload history of Instant edge.png, Instant Edge.png, Iedge-logo.png Magog the Ogre (talk) (contribs) 21:55, 28 January 2024 (UTC)Reply[reply]

For older requests, please see Commons:Requests for checkuser/Archives
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Requests_for_checkuser&oldid=847742226"