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]

Jurisdrew[edit]

Status: open • view • edit • history • watch
Filed: 21:39, 26 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Re-uploading files previously uploaded by confirmed sock Circesling (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log ). (Some with identical names e.g. File:Flag Of Pattani.svg, some with slight name differences e.g. File:Jammu and Kashmir Flag (1936-1953).svg/File:Flag Of Jammu and Kashmir (1936-1953).svg.) Paul_012 (talk) 21:39, 26 November 2023 (UTC)Reply[reply]


Kashyap's ReAction Channel[edit]

Status: open • view • edit • history • watch
Filed: 02:08, 26 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Accounts have repeatedly created the file File:Kashyap Jyoti Borah House.jpg under these accounts. (see logs) after having it speedily deleted multiple times. Both on enwiki and here, this user is blatantly using wikimedia projects as a webhost, and has even gotten locked for this behavior. Please also check for sleepers, as this account seems to have a lot of other accounts on other wikis. LemonSlushie (talk) 02:08, 26 November 2023 (UTC)Reply[reply]

Matlin[edit]

Status: resolved • view • edit • history • watch
Filed: 10:29, 19 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploading lots of Flickr files without categorization. Matlin was blocked multiple times in 2021-2022 for mass-upload without proper categorization, Kukurydziarz seems created to avoid scrutiny and evade the blocks on using the F2C tool. Account was blocked on Wikidata as socks of Matlin, but there is not obvious enough to be directly blocked. Therefore, a check is required. A1Cafel (talk) 10:29, 19 November 2023 (UTC)Reply[reply]

To expand upon the above, the block on WikiData was for possible block evasion. A1Cafel had requested a block at COM:ANB, but I had felt a bit uncomfortable with blocking here on the sole basis of that edit summary. I think that it may well warrant a check here if there's a pattern of similar behavior (which A1Cafel notes above) while also having a large sister wiki blocking Kukurydziarz as a possible sock of Matlin. The use of multiple accounts to evade a restriction on using the Flickr2Commons tool would be a cause for blocking the user. The usefulness of a check here would be to better establish whether or not these two accounts are technically connected. — Red-tailed hawk (nest) 04:53, 20 November 2023 (UTC)Reply[reply]

KittenBroEeev[edit]

Status: open • view • edit • history • watch
Filed: 04:52, 20 November 2023 (UTC)

Suspected related users[edit]


Rationale, discussion and results[edit]

Reason:Multiple account abuse, harassment (/ the last one can lead to a global ban)
1) Close interests. (Politics, flags, furry art)
2) On November 3rd, both users made edits related to the same topic on different Wikimedia projects (/ 1, / 2)
3) Most likely both users live in the same time zones, judging by what time they make edits.
4) Kitsune mentioned a person named Rashid on their blog (/ 3), KittenBroEeev`s name is Deffet-haz-Rashid (File:Информация.png)
5) KittenBroEeev was blocked on Russian Wikipedia for vandalism.(/ 4) He may have made a sockpuppet account to circumvent the blocking.
6) Almost immediately from the moment of registration Kitsune started to create articles, which requires at least a little previous experience in wiki projects. (/ 5, / 6)
7) Judging by the blog entry linked above, the alleged sockpuppet account was made to harass an X (previously known as Twitter) user named Kitsy(/ 7)
8) Both users are registred on Pikabu (/ 8) (/ 9) It is noteworthy that the first ChristyKitsune Pikabu account has posts of an offensive or sensitive nature, most likely with the intent to harass Kitsy and besmirch her name Kelly The Angel (talk) 04:52, 20 November 2023 (UTC)Reply[reply]

Finsoja[edit]

Status: resolved • view • edit • history • watch
Filed: 14:59, 15 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Disruptive user engaged in sock-puppetry with insults, death threats. Finsoja3 and Finsoja4 are already blocked, but confirmation is needed for "Thai-khmer learn", who uploaded again over File:HenryIIGospels.jpg. Yann (talk) 14:59, 15 November 2023 (UTC)Reply[reply]

  • Confirmed, among many others. This is a prolific LTA and the true initial account (master) is unclear. X-wiki tagging, if any, has been poor. I've used +L Oai iu aahhaahh as the oldest known confirmed account. Ro.wiki appears to use Blocau darius as the master--this account is not attached on the Commons. Эlcobbola talk 17:28, 15 November 2023 (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=825935749"