Wikidata

Wikidata:Requests for checkuser

Latest comment: 1 day ago by Sotiale in topic Gokcuzel

For the place to request CheckUser access, see Wikidata:Requests for permissions/CheckUser.
Requests for checkuser
This is the place to request investigations of abuse of multiple accounts or of other circumstances that require use of checkuser privileges.

Requesting a checkuser

Please don't ask us to run checks without good reason; be aware of the following before requesting:

  1. Checkuser is a means to choose for difficult cases. If multiple accounts show clear behavior patterns or editing type, please post on the administrator's noticeboard.
  2. Running a check will only be done to combat disruption on Wikidata, or as required to assist checkuser investigations on other Wikimedia wikis.
    • Valid reasons for running a check include, for example: 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. Do not post requests for fishing without any grounds.
  4. The privacy policy does not allow us to make a check that has the effect of revealing IP addresses. Do not post requests to compare IPs to accounts or IPs to IPs comparisons.
  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.

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.

To request a checkuser

Cases are created on subpages of Wikidata: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 (if the case has been archived). When editing an existing case, be sure to list/transclude the subpage here at the bottom.
Example
If you want to request a checkuser on User:John Doe, enter the text Wikidata:Requests for checkuser/Case/John Doe then click "Make a checkuser request". You will be taken to a page where you can fill out the request. Please make your request there brief and concise.
If this page is displaying outdated contents even after you refresh the page in your browser, please Purge.
For older requests, please see Wikidata:Requests for checkuser/Archives

Requests edit

Matlin edit

Latest comment: 1 day ago79 comments15 people in discussion

12 August 2023 edit

Rationale, discussion and results edit

Reason: Similar edits and both account use Polish. GZWDer (talk) 17:47, 12 August 2023 (UTC) Edit: Added Lizofon, same stuff. Jonathan Groß (talk) 17:55, 31 August 2023 (UTC)Reply

I will process this request within today. --Sotiale (talk) 01:25, 6 September 2023 (UTC)Reply

@Sotiale: Could you also find out the IP range and prevent them from creating more accounts? Jonathan Groß (talk) 08:58, 6 September 2023 (UTC)Reply
There are multiple ranges they use, and due to the nature of this user, there is no guarantee that they will only create an account here, so the hardblock is required, which seems difficult because it prevents existing users from editing. Because ranges are widely used, it is considered difficult to pinpoint them. --Sotiale (talk) 10:09, 6 September 2023 (UTC)Reply

Results:

  •   Confirmed: Matlin, Uguem caue te, Lizofon, Jan Borodo, AI Eros Hesther mo umw, Gintek, Ewa Lipton, ELOHESRAERAAJLOKSULPUME, Mariusz Beyger

Well.. I don't think they are different users, at least technically? --Sotiale (talk) 10:09, 6 September 2023 (UTC)Reply

They all have been blocked now. Thank you. --Lymantria (talk) 11:43, 6 September 2023 (UTC)Reply

16 September 2023 edit

Rationale, discussion and results edit

Reason: High volume edits, polish name, irresponsive. Lymantria (talk) 07:30, 16 September 2023 (UTC)Reply

added Pedoestis, mass edits, not-quite-fixing items previously created by other socks --Emu (talk) 08:54, 16 September 2023 (UTC)Reply

Results:

22 September 2023 edit

Rationale, discussion and results edit

Reason: High volume edits, Polish name, irresponsive. --Emu (talk) 07:14, 22 September 2023 (UTC)Reply

23 September 2023 edit

Rationale, discussion and results edit

Reason: Same editing pattern as all accounts above. If anyone is wondering where I get his new socks from, here's a jobs log on Mix'n'Match. He just keeps having fun there and has no intention of stopping. Regards Kirilloparma (talk) 03:58, 23 September 2023 (UTC)Reply

+ Umek Cuf. Easily spotted him again from here. Regards Kirilloparma (talk) 03:06, 26 September 2023 (UTC)Reply
+ Ajlokk Cuf. Yet another incarnation. Regards Kirilloparma (talk) 03:35, 27 September 2023 (UTC)Reply
+ Stinky Dumpling of Ume. Another one. Regards Kirilloparma (talk) 05:04, 28 September 2023 (UTC)Reply
Advocate from Sandtown seems to be another; the account was created after these were blocked. Peter James (talk) 16:58, 29 September 2023 (UTC)Reply
@Peter James, Kirilloparma: Please use {{checkuser}} when mentioning additional socks so their link here gets documented and it's easy for me to check them with a single click.--Jasper Deng (talk) 20:41, 29 September 2023 (UTC)Reply

All accounts listed above, up to Sotiale's last comment, are   Confirmed to be Matlin and blocked and tagged accordingly.--Jasper Deng (talk) 20:47, 29 September 2023 (UTC)Reply

10 October 2023 edit

Rationale, discussion and results edit

Reason: “If an organisation is a human it must be Matlin.“ (Kolja21) --Emu (talk) 13:12, 16 October 2023 (UTC)Reply

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

21 October 2023 edit

Rationale, discussion and results edit

Reason: He's back. Found him again via m'n'm jobs log. Kirilloparma (talk) 03:28, 21 October 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

26 October 2023 edit

Rationale, discussion and results edit

Reason: Matlin's brand new sock spotted on mix'n'match. Kirilloparma (talk) 01:31, 26 October 2023 (UTC)Reply

+ DengPsy, 65,089 mostly MnM-related edits in less than a month. --Emu (talk) 10:49, 26 October 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

30 October 2023 edit

Rationale, discussion and results edit

Reason: 11,207 mostly MnM-related edits in less than a week. --Emu (talk) 21:06, 30 October 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

31 October 2023 edit

Rationale, discussion and results edit

Reason: Yet another his newly created sock. Regards Kirilloparma (talk) 22:34, 31 October 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

02 November 2023 edit

Rationale, discussion and results edit

Reason: Another obvious sock by Matlin. The situation is already starting to get out of hand. Kirilloparma (talk) 03:34, 2 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

04 November 2023 edit

Rationale, discussion and results edit

Reason: Another pretty obvious sock by Matlin. --Emu (talk) 18:59, 4 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

06 November 2023 edit

Rationale, discussion and results edit

Reason: Another pretty obvious sock by Matlin. Multichill (talk) 22:34, 6 November 2023 (UTC)Reply

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:29, 2 December 2023 (UTC)Reply

14 November 2023 edit

Rationale, discussion and results edit

Reason: Another Matlin sock who has already made over 43,000 edits while no one before me has noticed him. The contributor continues to damage Wikidata and nothing changes. No comment. Kirilloparma (talk) 04:41, 14 November 2023 (UTC)Reply

+ Dromaiinae. Another one of his fresh socks. Should be blocked as soon as possible before he makes over 40,000 edits with this account as well. Regards Kirilloparma (talk) 18:20, 14 November 2023 (UTC)Reply
+ Smierdzace Kapsko Mue. And another one. Regards Kirilloparma (talk) 18:24, 14 November 2023 (UTC)Reply
Outside comment: Really strange that newly registered users may do so many edits per minute and thousands of edits without triggering any filter. --Denniss (talk) 13:53, 14 November 2023 (UTC)Reply
Indeed. It’s also baffling to me that WMF isn’t stepping in – I’m not an expert in Polish law but a restraining order doesn’t seem to be out of the question, legally speaking. (Yes, I have contacted them in the similar case some time ago, they didn’t even write back.) --Emu (talk) 20:31, 14 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:30, 2 December 2023 (UTC)Reply

17 November 2023 edit

Rationale, discussion and results edit

Reason: Him again. Should be blocked as soon as possible before he starts abusing m'n'm catalogs, update Wikidata button and as always his favorite HarvestTemplates to make 50,000 edits that no one will ever check. Kirilloparma (talk) 03:41, 17 November 2023 (UTC) Regards Kirilloparma (talk) 03:41, 17 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:30, 2 December 2023 (UTC)Reply

22 November 2023 edit

Rationale, discussion and results edit

Reason: Same editing pattern as all socks above. Regards Kirilloparma (talk) 05:52, 22 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:30, 2 December 2023 (UTC)Reply

23 November 2023 edit

Rationale, discussion and results edit

Reason: It's him again. Already made 20,000+ edits. Kirilloparma (talk) 02:16, 23 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:30, 2 December 2023 (UTC)Reply

24 November 2023 edit

Rationale, discussion and results edit

Reason: His new sock spotted from here. Regards Kirilloparma (talk) 04:47, 24 November 2023 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 10:30, 2 December 2023 (UTC)Reply

25 November 2023 edit

Rationale, discussion and results edit

Reason: Another one of his socks. Regards Kirilloparma (talk) 04:50, 25 November 2023 (UTC)Reply

Results:   Completed

--Sotiale (talk) 10:23, 2 December 2023 (UTC)Reply

Some necessary measures have been implemented, but this could soon be avoided. --Sotiale (talk) 10:31, 2 December 2023 (UTC)Reply
@Sotiale: Thank you so much!
> Some necessary measures have been implemented, but this could soon be avoided
By that you mean that you have found a better way to track down the new socks of this user? Regards Kirilloparma (talk) 02:12, 31 December 2023 (UTC)Reply
No, it just meant that the routine and usual methods would be implemented. Sadly, I can't do anything outside of MediaWiki functionality unless new features are developed and deployed. --Sotiale (talk) 15:39, 3 January 2024 (UTC)Reply

31 December 2023 edit

Rationale, discussion and results edit

Reason: Matlin has once again created a new sock. Kirilloparma (talk) 02:17, 31 December 2023 (UTC)Reply

Results:   Confirmed.--Jasper Deng (talk) 07:17, 3 January 2024 (UTC)Reply

03 January 2024 edit

Rationale, discussion and results edit

Reason: As soon as he was recently blocked, he created a new sock. Kirilloparma (talk) 02:33, 3 January 2024 (UTC)Reply

Results:   Confirmed.--Jasper Deng (talk) 07:16, 3 January 2024 (UTC)Reply

06 January 2024 edit

Rationale, discussion and results edit

Reason: Another brand-new sock. Regards Kirilloparma (talk) 04:25, 6 January 2024 (UTC)Reply

Results: @Kirilloparma: Please provide specific evidence connecting them to the master; a check cannot otherwise be done.--Jasper Deng (talk) 23:47, 7 January 2024 (UTC)Reply

@Kirilloparma:   Declined until you provide such evidence.--Jasper Deng (talk) 19:56, 10 January 2024 (UTC)Reply
@Jasper Deng:. This account has the same patterns as all the previous blocked socks. He creates account - and on the same day massively launches jobs on Mix-n-match, and does with the same catalogues he worked on the previous banned account. Then he immediately starts doing mass batches, ending with 20k edits on the first day of account. These batches are no brainer syncs of outdated incorrect data from Mix-n-match back to WD where it was already fixed and removed. Some of these edits are correct, but percentage of errors is just way too high. After that he's getting exactly the same comments on his talk page by various users like here where someone says he's mistaken the organisation with a person, i.e. bringing back all the fixed issues that remain unresolved on MnM, but were fixed on WD. This behaviour has been repeated for six months on each of these socks. I personally fixed these sync errors of him for only 1 property within days after they were imported by his original account and stayed untouched for 2 years. He just doesn't understand that those batches need to be made and fixed via the API on Mix-n-match, not moved back to WD, no matter how you try to explain it to him. At this point this account already has 70k edits. This is not typical behaviour for new created accounts, right? Solidest (talk) 14:03, 16 January 2024 (UTC)Reply
@Solidest:   Confirmed now that I have enough evidence. The point is that checks cannot be done without evidence provided, otherwise I could check anyone on the grounds that they are "another brand-new sock", which is against the privacy policy.--Jasper Deng (talk) 22:59, 16 January 2024 (UTC)Reply

20 February 2024 edit

Rationale, discussion and results edit

Reason: Making mass edits on same items as blocked puppets Cipka1234, Sretetete and Multistress, which have all been blocked as resurgences of Matlin. Example. + obvious Polish tropism. Frenchl (talk) 07:39, 20 February 2024 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 08:37, 24 March 2024 (UTC)Reply

08 March 2024 edit

Rationale, discussion and results edit

Reason: Edits to Matlins userspace. Also starts off by using obscure mass-edit tools such as Plnode, clearly indicating this is not a new user. Pattern of edits seems to fit with earlier pattern of edits. Impersonating Magnus Manske is a sanctionable in itself. Infrastruktur (talk) 15:29, 8 March 2024 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 08:37, 24 March 2024 (UTC)Reply

15 March 2024 edit

Rationale, discussion and results edit

Reason: Starts off by using obscure mass-edit tools such as Plnode, clearly indicating this is not a new user. Pattern of edits seems to fit with earlier pattern of edits. Doing unattended edits without getting bot approval. Infrastruktur (talk) 15:29, 8 March 2024 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 08:37, 24 March 2024 (UTC)Reply

18 March 2024 edit

Rationale, discussion and results edit

Reason: Same as above. Infrastruktur (talk) 12:38, 18 March 2024 (UTC)Reply

Results:   Completed

--Sotiale (talk) 08:36, 24 March 2024 (UTC)Reply

17 April 2024 edit

Rationale, discussion and results edit

Reason: Similar to the above (new user making lots of mass edits—many of Polish relevance—using QuickStatements and other gadgets/tools). Mahir256 (talk) 21:20, 17 April 2024 (UTC)Reply

I also identified this user as a resurgence of Matlin. Frenchl (talk) 03:09, 25 April 2024 (UTC)Reply
The pseudo-Arabic username says it all: "Chase away the Emu" (the admin that blocked Matlin's sock puppet accounts). --Kolja21 (talk) 17:51, 6 May 2024 (UTC)Reply
I have been contacted by said user with all kinds of accusations in Matlin’s typical style, even including threats against “disclosing its contents to third parties”. --Emu (talk) 18:26, 6 May 2024 (UTC)Reply

Results:

  Completed Batch processed in the request below. See results below. --Sotiale (talk) 08:29, 10 May 2024 (UTC)Reply

8 May 2024 edit

Rationale, discussion and results edit

Reason: Similar to the above (new user making lots of mass edits—many of Polish relevance—using QuickStatements and other gadgets/tools). --Emu (talk) 19:26, 8 May 2024 (UTC)Reply

Results:   Completed

@Emu: It feels like a departure from the way they create many accounts. --Sotiale (talk) 08:28, 10 May 2024 (UTC)Reply

Gokcuzel edit

Latest comment: 1 day ago2 comments2 people in discussion

09 May 2024 edit

Rationale, discussion and results edit

Reason: The relevant user constantly creates different users and adds non-notable items. Since I'm from Turkey, I can say that usernames are randomly acquired. What I can detect is as follows. Zafer (talk) 07:51, 9 May 2024 (UTC)Reply

Results:   Doing… It smells like a fish tank, but since there are so many of them, it may take some time. --Sotiale (talk) 08:34, 10 May 2024 (UTC)Reply

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Requests_for_checkuser&oldid=2149463943"