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.

nothing found

Requests[edit]

Roberto Sarfatti[edit]

Rationale, discussion and results

Reason: New account with similar contributions as Giorgio's other socks, created twelve days after the blockage of Fefecece, replying to @Krd. Investigation to determinate relation should be needed. 83.61.247.43 10:37, 26 February 2024 (UTC)Reply[reply]

  •  Comment - I'll leave this for @Krd: or @Jameslwoodward: since they are familiar with it (and the former pinged above). This request does not provide evidence or diffs ("New account with similar contributions as Giorgio's other socks" is hardly helpful) and thus is not accessible to a CU (me) not already familiar with the user. (This even has overlap with A3cb1.) Эlcobbola talk 16:05, 26 February 2024 (UTC)Reply[reply]


Matlin[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Mass Flickr upload without any category, which is similar to what Matlin and his sock done previously. Has been blocked on Wikidata, but this has not been checked via a Checkuser. A check is necessary in this case. A1Cafel (talk) 03:33, 26 February 2024 (UTC)Reply[reply]

Marcelo Rodrigues da Silva Estêvão[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: First of all, the names are very similar. Second, both accounts are obsessed with upload images of "Nadja Pessoa". On Fev. 22, Marcelo Rodrigues da Silva Estêvão (talk · contributions · Move log · block log · uploads · Abuse filter log was blocked for their insistence in uploading copyvios. Many of that copvyos are pictures of Nadja Pessoa. Today, Marcelo Rodrigues 2109 (talk · contributions · Move log · block log · uploads · Abuse filter log uploaded another picture of Pessoa, a picture taken from Twitter. I'm pretty sure these two accounts are operated by the same person to try to evade blocking. Kacamata! Dimmi!!! 23:05, 25 February 2024 (UTC)Reply[reply]

Nizam Alif[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Nizam Alif is glocked. Vandalising troll from Java sharing similar behavior, but I'm not sure if that are their socks. --Achim55 (talk) 10:10, 25 February 2024 (UTC)Reply[reply]

SonyGM[edit]

Hello! This user's contributions to the English-language Wikipedia made me wonder if they are another sockpuppet of Livioandronico2013. I noticed that they swapped a photo of the City of San Marino to one uploaded by Messapi, an identified sockpuppet. They seem to be editing crosswiki. IgnatiusofLondon (talk) 03:53, 25 February 2024 (UTC)Reply[reply]

Also adding Grosseto2 (talk contribs Luxo's SUL deleted contribs logs block user block log ) with same usual xwiki modus operandi and EXIF data as other Livioandronico2013 socks.--A09 (talk) 15:56, 25 February 2024 (UTC)Reply[reply]
It appears to be another pair of this LTA's socks, created (possibly?) after the latest checkuser request. 83.61.247.43 12:21, 26 February 2024 (UTC)Reply[reply]
 Info: Messapi's latest contributions before their block are dated one month ago. Note also that this user is blocked both in Commons and Meta (global). 83.61.247.43 12:25, 26 February 2024 (UTC)Reply[reply]

Jdbxhdjdjdjd[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason:See [2]. 💚Kelly The Angel (Talk to me)💚 05:11, 16 February 2024 (UTC)Reply[reply]

Confirmed Jdbxhdjdjdjd = Dudbdudiwo
Unlikely Commodeprd
Stale Алексей Икербекмуйлагбабиев
--Krd 06:07, 16 February 2024 (UTC)Reply[reply]

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