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
Artículo bueno.svg Confirmed Symbol confirmed.svg Technically indistinguishable
Likely Symbol version generic.svg Possilikely
Symbol possible vote.svg Possible Symbol unlikely.svg Unlikely
Symbol unsupport vote.svg Inconclusive Symbol unrelated.svg Unrelated
Symbol no support vote.svg No action 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

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.
  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.
  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.
  5. Requests to run a check on yourself will be declined.

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‎ (1 P)
Commons:Requests for checkuser/Case/Taki2006

Requests[edit]

Taki2006[edit]

Status: Symbol unrelated.svg open • view • edit • history • watch
Filed: 19:30, 26 May 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

ZakariaDjaafar has same actions [1] on Algeria flags files (and north africa former dynasties) than users @ZakariaDjaafar, Takiva, ⵜⴰⴽⵉ, Nedrko, and ⵎⴰⵙⵏⵙⴰ: , users who are pupetsocks of the Takiva. --Poudou99 (talk) 19:30, 26 May 2023 (UTC)Reply[reply]

Hfive5sgd2 May 25[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

I already blocked them, but please check for sleepers. Also could you please block the range(s), as this is beginning to be tedious. Thanks, Yann (talk) 13:24, 25 May 2023 (UTC)Reply[reply]

  • Cyberduck icon.png It looks like a duck to me - We are not unaware of range blocks. When four different CUs have looked into this case over two months, you may and should assume possible range blocks have already been made (they have). As indicated below, there is a large number of ranges. We cannot make /34, /32 -wide blocks on dozens of ranges without unacceptable collateral damage--simply RBI. Checkuser is not magic pixie dust. There is also no real purpose in checking for sleepers, as spambots are not the same as "real human" LTAs. The latter create pools of sleepers to draw from when one account is blocked, so finding sleepers prevents future disruption. The former, however, this case, create single-use accounts that upload one or several images and then are abandoned never to be used again. (I don't see that any account has an activity window longer than several minutes--if I've missed one, please provide it) Accordingly, finding these accounts does nothing to prevent future disruption, which is a prerequisite for a check. Эlcobbola talk 13:47, 25 May 2023 (UTC)Reply[reply]
  • Even short term range would be useful. Don't spambots create more than one account at the time? How blocking sleepers before they are used are not preventing future disruption? I don't get that. Yann (talk) 13:53, 25 May 2023 (UTC)Reply[reply]
Let's take the first five accounts from your request as examples:
Xoilactvio
  • 10:50, 25 May 2023 - created
  • 10:51, 25 May 2023 - copyvio 1
  • 10:52, 25 May 2023 - copyvio 2
Tk88aicasino
  • 06:34, 25 May 2023 - created
  • 06:35, 25 May 2023 - copyvio (only 1)
Bongdalusp
  • 08:03, 24 May 2023 - created
  • 08:05, 24 May 2023 - copyvio (only 1)
Sm66nhaca
  • 05:41, 24 May 2023 - created
  • 05:42, 24 May 2023 - copyvio (only 1)
Tk88cz
  • 09:05, 23 May 2023 - created
  • 09:06, 23 May 2023 - copyvio (only 1)
1) They are not created in batches ("Don't spambots create more than one account at the time?") and 2) As I said, these are spambots that are created, immediately upload, then are never used again. With the way rounding works, we would have to to find them the exact minute of their creation to prevent disruption--i.e., they cannot realistically be blocked before use ("How blocking sleepers before they are used are not preventing future disruption"). Эlcobbola talk 14:44, 25 May 2023 (UTC)Reply[reply]



A3cb1[edit]

Status: Symbol unrelated.svg open • view • edit • history • watch
Filed: 11:35, 16 May 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Ulcarco77 is a new user requesting undeletion of files uploaded by Lûgnûg, another sock of A3cb1. This is the usual partern for A3cb1's socks: uploading a few files, and then request undeletion of A3cb1's socks files. Yann (talk) 11:35, 16 May 2023 (UTC)Reply[reply]

Artículo bueno.svg Confirmed, as well as Custainor99 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log ) and Lødrionatta (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log ). --Krd 03:58, 18 May 2023 (UTC)Reply[reply]
Please check Janiken98, idem as Ulcarco77. Yann (talk) 16:43, 22 May 2023 (UTC)Reply[reply]
Janiken98 is Artículo bueno.svg Confirmed. Эlcobbola talk 16:56, 22 May 2023 (UTC)Reply[reply]
Added one more suspected sock and reopened. Ankry (talk) 15:58, 25 May 2023 (UTC)Reply[reply]
I've added Marck Giannini as well. An IP is inserting all his uploaded pictures on it.wiki on A3cb1's topic articles. Thanks --Ruthven (msg) 07:20, 26 May 2023 (UTC)Reply[reply]



Stephane szyller[edit]

Status: Symbol unrelated.svg open • view • edit • history • watch
Filed: 15:51, 14 May 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Create the same DR with almost identical (invalid) reason at File:Michale Boganim from "Tel Aviv Beirut" at Red Carpet of the Tokyo International Film Festival 2022 (52461587778).jpg. A1Cafel (talk) 15:51, 14 May 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=767340766"