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 Likely
Symbol version generic.svg Possilikely Symbol possible vote.svg Possible
Symbol unlikely.svg Unlikely Symbol unsupport vote.svg Inconclusive
Symbol unrelated.svg Unrelated 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‎ (empty)
nothing found

Requests[edit]

AXXXXK[edit]

view • edit • history • watch
Filed: 10:18, 14 January 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: LTA, see COM:AN/B#又一城1998 and [1]. This guy keeps creating new accounts daily, posting selfies and other nonsense. May be you could block the range, or at least block dormant accounts. Yann (talk) 10:18, 14 January 2023 (UTC)Reply[reply]

  • As a general proposition, when checkusers are aware of an LTA with this level of ongoing disruption, the possibility of range blocks has already been examined. I've nevertheless looked again and there remains nothing to do here--this user is seldom, if ever, on the same range twice and is even spoofing their UA. Range blocks would do nothing but cause collateral damage while not even preventing the disruption. RBI. Эlcobbola talk 17:59, 17 January 2023 (UTC)Reply[reply]

Yoshi773[edit]

view • edit • history • watch
Filed: 00:19, 14 January 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: obvious puppetery; very similar name, very similar uploadings(sussy licensed images) and biggest proof:deleted image uploaded by Yoshi773 later uploaded by Yoshi3620). ----modern_primat ඞඞඞ TALK 00:19, 14 January 2023 (UTC)Reply[reply]

also Yoshi773's uploadings should be put in nomination for deletion. ----modern_primat ඞඞඞ TALK 00:23, 14 January 2023 (UTC)Reply[reply]
Pictogram voting comment.svg Comment I blocked Yoshi773 for 2 weeks for copyvios, and Yoshi3620 indef. All files deleted. Yann (talk) 09:53, 14 January 2023 (UTC)Reply[reply]
  • Declined - "Checkuser is a last resort for difficult cases" (COM:RFCU), not for "obvious puppetry" (note also that {{Duck}} is a "request declined" indicator). Yoshi3620 is already blocked, so a check would not be necessary to prevent disruption. Эlcobbola talk 17:18, 17 January 2023 (UTC)Reply[reply]

SwissArmyGuy[edit]

view • edit • history • watch
Filed: 03:13, 13 January 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: See the underlying topics here and there.

And how do you like this? Funny, isn't it: Yann never mentioned SwissArmyGuy.

If you look at SwissArmyGuy's bio from the very beginning (at enwiki), you'll see two very distinct patterns. First, he is eligible to the Darwin Awards for the manner in that his accounts are always ruined. He tries to hound others, and always in such a foolish way that he gets blocked himself. His second feature is a very poor English. His wording is often totally incomprehensible (as shown at Meta), and his understanding of the rules and talk pages is likewise. (Very poor Russian as well, to the same degree. I can't figure out his ethnicity and his diagnosis so far.)

And last but not least: in my ten years of WM tenure I'd never seen a person who would hound me that much. — Mike Novikoff 03:13, 13 January 2023 (UTC)Reply[reply]

  •  Not done - Ostrich Parade is checkuserblocked on meta which, as an SUL account, is valid across projects. No redundant Commons check is needed. We cannot comment on IPs. Эlcobbola talk 17:44, 13 January 2023 (UTC)Reply[reply]

MadroDragon[edit]

view • edit • history • watch
Filed: 05:15, 9 January 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Today MadroDragon was blocked for repeated uploads of copyvios related to a news event in Mexico and whose images were used in the Spanish Wikipedia article. Despite this, MadroDragon continued to edit Wikipedia without much troubles. Now few minutes ago ElWikipedistaPandi is now uploading new images about the same article, but MadroDragon and Cirilokuaz are using the files in Spanish Wikipedia. It's notable to check that Cirilokuaz is indef blocked in Commons. Taichi (talk) 05:15, 9 January 2023 (UTC)Reply[reply]

A1Cafel[edit]

view • edit • history • watch
Filed: 19:55, 3 January 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: See Commons:Administrators'_noticeboard/User_problems#Massive_image_deletion_requests_by_user_A1Cafel

This is a user who has a long history of problem behaviour centred around deletion (also uploading content with the same issues, then getting very defensive to keep it). Topic banning has been required previously. They're also infamously uncooperative and uncommunicative. They have a long history of simply issuing speedy deletes and DRs, then avoiding any engagement to discuss them. These speedies have often been far from useful or appropriate, [2] but relied on a simplistic "letter of the law" approach.

Here we see a rather peculiar overlap of sequential edits by two users, both in Hong Kong, to an image with no obvious connection to HK. It's not a disruptive edit, if it's the same editor then we might just overlook it as "non-harmful editing whilst logged out". File:Pacific_Plaza_in_1999.jpg

I believe they're still TBanned from using speedy deletions. Second appeal on the topic ban.

In which case these: [3] [4] [5] [6] become not just IP editing, or "accidentally logged out", but an active attempt to avoid such a TBAN. Andy Dingley (talk) 19:55, 3 January 2023 (UTC)Reply[reply]

Checkusers cannot comment on whether a user used a specific IP address. Still the raised concern appears reasonable and justifies a check, and data Artículo bueno.svg confirms that the user at more than two occasions logged out of their account to perform edits affected by the topic ban.
I cannot say how many such edits exactly have been made. In any case they appear to be few compared to the total activity of the user, though some happened. I leave possible sanctions up to another admin. --Krd 15:37, 14 January 2023 (UTC)Reply[reply]
@Krd I'd be willing to consider the sanctions to apply, but would need some more information. The "total activity of the user" is, of course, quite high. Can you give a ballpark estimate of abusive logged-out edits you can attribute to the user (i.e. are we talking 5 edits, or 100) and describe the types of edits in general terms? And can you say about how long you can confirm this has been going on (i.e. last week or 90 days)? Ultimately, although I'd be happy to act on this information, this is the kind of thing that makes me wish we had an Arbitration Committee (by the way, Commons:Village_pump/Proposals#Arbitration_Committee_for_Commons is going on right now!), or at least made me wish I were a checkuser. :) —‍Mdaniels5757 (talk • contribs) 18:53, 15 January 2023 (UTC)Reply[reply]
I received an email from Krd with some answers and explaination. Blocked for 2 weeks. —‍Mdaniels5757 (talk • contribs) 15:37, 16 January 2023 (UTC)Reply[reply]

Bbeyza000[edit]

view • edit • history • watch
Filed: 22:50, 3 January 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: these accounts uploaded very similar images(screen photo, not notable, both are turkish, near time uploading). and they are suspicious, maybe they are sockpuppet or meatpuppet? images(i already tagged them with speedydelete): https://web.archive.org/web/20230103224505/https://commons.wikimedia.org/wiki/File:Halil_bey_cami.jpg , https://web.archive.org/web/20230103224412/https://commons.wikimedia.org/wiki/File:Gen%C3%A7_Mehmet_Pa%C5%9Fa_Camii.jpg - also for articles on tr wikipedia: https://web.archive.org/web/20230103224802/https://tr.wikipedia.org/w/index.php?title=Halil_Bey_Cami:&action=history , https://web.archive.org/web/20230103224821/https://tr.wikipedia.org/w/index.php?title=Gen%C3%A7_Mehmet_Pa%C5%9Fa_%28%C3%96rtmeli%C3%B6n%C3%BC%29_Camii&action=history ----modern_primat ඞඞඞ TALK 22:50, 3 January 2023 (UTC)Reply[reply]

also using same site as reference: https://kulturportali.gov.tr/turkiye/tokat/kulturenvanteri/genc-mehmet-pasa-ortmelionu-camii , https://www.kulturportali.gov.tr/turkiye/tokat/kulturenvanteri/halil-bey-camii
more web archive links: https://web.archive.org/web/20230103224821/https://tr.wikipedia.org/wiki/Halil_Bey_Cami: , https://web.archive.org/web/20230103225527/https://tr.wikipedia.org/wiki/Gen%C3%A7_Mehmet_Pa%C5%9Fa_%28%C3%96rtmeli%C3%B6n%C3%BC%29_Camii ----modern_primat ඞඞඞ TALK 22:56, 3 January 2023 (UTC)Reply[reply]
-
lets count that account too: Bbeyza000, i have less about this account but still got something.
links: https://web.archive.org/web/20230103234812/https://commons.wikimedia.org/wiki/File:Ak%C5%9Femseddin_camii.jpg - https://web.archive.org/web/20230103234852/https://tr.wikipedia.org/wiki/Ak%C5%9Femsettin_camii - https://web.archive.org/web/20230103234927/https://commons.wikimedia.org/wiki/File:Alaca_cami.jpg - https://web.archive.org/web/20230103234954/https://tr.wikipedia.org/wiki/Alaca_mescit_camii ----modern_primat ඞඞඞ TALK 23:56, 3 January 2023 (UTC)Reply[reply]
(copyvio images, not notable, turkish, near time uploading). ----modern_primat ඞඞඞ TALK 23:57, 3 January 2023 (UTC)Reply[reply]
i didnt mentioned, but all of them for not notable mosque articles. i have suspicion about these accounts managed by a center? ----modern_primat ඞඞඞ TALK 23:58, 3 January 2023 (UTC)Reply[reply]
  • I am inclined to decline this request. Evidence provided suggests a connection, but does not demonstrate this to be "a last resort for difficult cases" (COM:RFCU). For example, the earliest notice any of these three accounts received was Cansayar1 at 22:18, 3 January 2023‎. Only a single upload from any of the three has occurred after that notice, File:Örtmeliönü Camii.jpg. This is very meagre disruption indeed, and is not yet at a level suggesting a CU is needed for resolution (again, "a last resort for difficult cases"). There is not, for example, adeqaute evidence that this single upload was done to evade detection or sanctions or otherwise engage in abusive use of multiple accounts. I'll leave this open in case another CU wants to opine. Эlcobbola talk 22:21, 6 January 2023 (UTC)Reply[reply]
    https://tr.wikimedia.org/wiki/VikiSal%C4%B1_Bulu%C5%9Fmalar%C4%B1/2023-01-03
    in here, it says: ""Son günlerde Vikipedi'de artan öğrenci ödevi girişleri (örneğin Samsun, Tokat civarında türbeler hakkında bilgi girilmesi) üzerine konuşuldu. Topluluğun bu sıralarda takip ettiği, ilgilendiği bir ödev yok; ödev amaçlı girişlerden haberdar oldukça o içerikleri giren öğrencilerle irtibat kurup hocalarına ulaşmaya ve yardımcı olmaya çalışıyoruz.""
    google translated: Recently, there has been talk about the increasing number of student homework entries on Wikipedia (for example, entering information about shrines around Samsun, Tokat). There is no homework that the community is following or interested in at this time; As we become aware of the homework entries, we contact the students who enter that content and try to reach their teachers and help them.
    @Elcobbola maybe they are students, i dont know. thank you for responding. ----modern_primat ඞඞඞ TALK 17:48, 7 January 2023 (UTC)Reply[reply]
    As I said above, evidence provided suggests a connection. Meatpuppetry is also an abusive use of multiple accounts, so this is potentially actionable whether students or a single person (I agree this appears the former). There is not, however, currently disruption rising to the level that requires CU involvement. I've nominated the users' uploads for deletion and warned both Cansayar1 and Türk var mı beyler about COM:DWs and the prohibition on abuse of multiple accounts. (Bbeyza000's edits are different--simple COM:NETCOPYVIOs instead of photographs of computer screens--so I'm erring on not considering them related for the time being.) If either account continues to upload problematic content, or a new account emerges, please let me know as that may be sufficient evidence of disruption (e.g., attempting to avoid scrutiny/sanctions of which they were warned). Эlcobbola talk 16:06, 9 January 2023 (UTC)Reply[reply]

Since may previous comment, Cgrkrcc3232‎ has uploaded similar images (photographs of computer screens) and was checked on that basis. In addition to behaviour, Cgrkrcc3232‎ and Cansayar1 are both on two disparate ranges with the same device, so I would say at worst Likely for those two accounts. Many other users are in the same ranges with similar behaviour, which may support this being a class or otherwise multiple persons with a common link. Türk var mı beyler is among them, so Symbol version generic.svg Possilikely. I've blocked certain others with more recent contributions, but left others as the transitory nature of class editing does not suggest mass blocking (and indeed the significant time to evaluate behaviour) is necessary to present disruption. Эlcobbola talk 19:57, 10 January 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=725768297"