Wikidata

Wikidata:Requests for checkuser

(Redirected from Wikidata:RFCU)
Latest comment: 16 hours ago by Infrastruktur in topic Selamiben

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

Anita maulia rosalina

edit
Latest comment: 5 days ago1 comment1 person in discussion

08 July 2024

edit

Rationale, discussion and results

edit

Reason: I blocked the latter three for recreating items on Soo Hana. Items on this subject also mentioned Suwanda Sitorus as partner, also mentioned in Q127202858 by Zahriana. All seems related to m:Special:CentralAuth/Suwanda_Sitorus/c:Category:Sockpuppets of Suwanda Sitorus. Lymantria (talk) 16:11, 8 July 2024 (UTC)Reply

Results:

Matlin

edit
Latest comment: 2 days ago83 comments16 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

18 May 2024

edit

Rationale, discussion and results

edit

Reason: Similar MO as before: new user using gadgets to make a lot of edits and to create many new items, all with Polish relevance. Lymantria (talk) 07:53, 18 May 2024 (UTC)Reply

Results:   Confirmed and KustoszkaCleaner blocked. --Sotiale (talk) 14:44, 22 May 2024 (UTC)Reply

11 July 2024

edit

Rationale, discussion and results

edit

Reason: Same MO (semi-automated mass edits by new user). Lymantria (talk) 07:05, 11 July 2024 (UTC)Reply

  Info Globally locked. --Wüstenspringmaus talk 08:17, 11 July 2024 (UTC)Reply

Results:

MrProperLawAndOrder

edit
Latest comment: 6 days ago46 comments14 people in discussion

Rationale, discussion and results

edit

Reason: The user frequently cites EnWiki policy but doesn't have an account on EnWiki. In addition Edoderoo voiced additional suspicion at https://www.wikidata.org/wiki/Wikidata:Administrators%27_noticeboard#User:MrProperLawAndOrder ChristianKl ❪✉❫ 21:54, 17 June 2020 (UTC)Reply

Results: @Edoderoo: Which "5-letter-long user" do you refer to here? Other CheckUser's (@Sotiale, BRPever, علاء:) are free to disagree, but I'm not fully comfortable running a check with only the evidence that they cite enwiki policy without having edited there.--Jasper Deng (talk) 01:23, 19 June 2020 (UTC)Reply

That other user is Jura1, a user on Telegram asked me for this as he/she had the feeling they were the same user. I learned that they took part in the same discussion(s), which made it borderline abusive as I as told. That is all I know so far. Edoderoo (talk) 04:32, 19 June 2020 (UTC)Reply
@Edederoo: What evidence is there? I don't think it's characteristic of Jura to cite external policies.--Jasper Deng (talk) 08:00, 19 June 2020 (UTC)Reply
Agree, I cannot see how MrProperLawAndOrder and Jura1 should be identical. However, User:Jura1 made two related comments on WD:AN in May regarding User:MrProperLawAndOrder (new account from early April), but without mentioning their user name:
In other words, the assumption is that User:MrProperLawAndOrder is an account operated by the person who received a global community ban at meta:Requests for comment/Global ban for Tobias Conradi in 2015, and who is assumed to have returned with lots IP activity and potentially some undeclared accounts since then. I think that quite some users here would agree that this person has never really left Wikimedia projects after the global ban, as they have been around pretty much all the time. Their fields of work, editing patterns, technological skills, formatting quirks, inability to accept consensus against their own position, and tendency to drift into pretty aggressive, accusive conversation manners in conflicts are all remarkable. User:MrProperLawAndOrder looks in many regards meanwhile like a sock of said banned user.
If that assumption was correct, User:MrProperLawAndOrder would have been a rather promising attempt for a clean start, as there was in the beginning not much conflict, but a lot of rather productive work for which they earned some applause from other users. Meanwhile, however, there have been some discussions in June that do not look promising any longer, and are reminiscent of said banned user's behavior.
I am not sure whether I should be happy about this request in the way how it was made. It is also unclear to me whether checkuser can help here at all, as I do not expect them to operate other accounts in parallel for which checkuser data is still available. However, the IP ranges usually used by the user in question are well-known (Telefonica ranges geolocating in Berlin, and sometimes also Hamburg-based IPs of another provider). That said, I would not be surprised if User:MrProperLawAndOrder would be blocked indefinitely rather soon anyways for behavioral reasons.
Disclaimer: recently I had some contact with them as well on Property talk:P213 and the corresponding property. ---MisterSynergy (talk) 13:06, 19 June 2020 (UTC)Reply
@Jasper Deng, Sotiale: I suggest what Jura said in Wikidata:Administrators'_noticeboard/Archive/2020/04#Please_semi is about Tobias Conradi, and both the IP and MrProperLawAndOrder edited Property_talk:P7902. And there is almost certainly some information about this user in checkuserwiki.--GZWDer (talk) 13:34, 19 June 2020 (UTC)Reply
  • On the grounds provided by @MisterSynergy, GZWDer: (but emphatically not the original evidence, which would never have been sufficient to run a check), I declare them   Likely Tobias Conradi based on both technical evidence and the observed behavior. Therefore, their block is upgraded to indefinite as a sock.--Jasper Deng (talk) 19:35, 19 June 2020 (UTC)Reply
@Sotiale, BRPever, علاء: Please lock this account and block any relevant IP ranges.--GZWDer (talk) 00:34, 20 June 2020 (UTC)Reply
Yes, I will review it and handle it soon. --Sotiale (talk) 06:49, 20 June 2020 (UTC)Reply

27 June 2021

edit

Rationale, discussion and results

edit

Reason: Global ban since 2015, creates socks or works as an IP with a similiar pattern: “in the beginning not much conflict, but a lot of rather productive work for which they earned some applause from other users [but then] some discussions […] that do not look promising any longer” (see above). The “not so promising phase“ has begun.

User:MisterSynergy has compiled a list of typical patterns (see above):

  1. Field of work: Interest in authority data (“Normdatentroll, SFZ-Troll, ISNI-Troll”, especially around GND ID (P227)-related properties such as Deutsche Biographie (GND) ID (P7902) (also the main field of activity in 2021)
  2. editing patterns: masses of edits in said field, mostly well-intentioned and productive but as the user has little to no ability to listen and discuss productively, not-so-great edits aren’t removed.
  3. technological skills as demonstrated in his work on Property talk:P7902
  4. formatting quirks such as
    • raw data mingled with complaints about data quality: compare 2020 vs 2021
    • endless lists with varying degrees of usefulness: 2019 vs 2021
  5. inability to accept consensus against their own position
  6. tendency to drift into pretty aggressive, accusive conversation manners in conflicts are all remarkable

For further reading on IP ranges and the questionable usefulness of CU and other actions see above.

Just for reference, the following recurring elements of the user’s behavior might lie in the future:

--Emu (talk) 15:06, 27 June 2021 (UTC)Reply

+1. Same user as 77.183.151.129 and User:Michael Montag. --Kolja21 (talk) 17:10, 28 June 2021 (UTC)Reply
Based on username and field of work, User:Matthias_Mittwoch is another one to look at. —MisterSynergy (talk) 11:54, 30 June 2021 (UTC)Reply

Results: We have Michael Montag and HumanAFuser   Confirmed to be the same. I would say (with the behavioral evidence) that it is   Likely that they are Tobias Conradi.--Jasper Deng (talk) 07:13, 30 June 2021 (UTC)Reply

@Jasper Deng: Items created through https://quickstatements.toolforge.org/#/batch/57984 and https://quickstatements.toolforge.org/#/batch/57971 have very near resemblances with item created through https://quickstatements.toolforge.org/#/batch/35535 b MrProperLawAndOrder. Given the evidence, I think to have to proceed as in 2020. --Epìdosis 08:08, 30 June 2021 (UTC)Reply
@Epìdosis: Wikidata have no policy to delete pages merely because of they are created by blocked users, not is it a established practice.--GZWDer (talk) 09:13, 30 June 2021 (UTC)Reply
@GZWDer, Jasper Deng: I perfectly agree, of course! With "I think to have to proceed as in 2020" in fact I meant the necessity of blocking the accounts as socks, not of deleting the items they created; in fact, as in 2020, I am against their deletion (and they weren't deleted in 2020) and I support their enrichment instead. --Epìdosis 11:12, 30 June 2021 (UTC)Reply
@Epìdosis: These two accounts are now locked.--GZWDer (talk) 14:37, 30 June 2021 (UTC)Reply

24 February 2023

edit

Rationale, discussion and results

edit
  1. Field of work: check, GND and similar authority data
  2. editing patterns: should be obvious from Special:Contributions/Humanisator
  3. technological skills: as always, Tobias shows quite some talent in his endeavours
  4. formatting quirks, inability to accept consensus against their own position and tendency to drift into pretty aggressive manners: see this textbook case including this: “It seems as if the goal of Kolja21 posting here is not to improve items about entities of type human that have or may have a P227 claim in the Wikimedia project named "Wikidata", but to create drama to intimidate a contributor and maybe get him kicked-out”

To be honest, I’m not even sure that we need a RfC per w:en:WP:RBI and w:en:WP:DUCK, but Epìdosis suggested one @Kolja21, Epìdosis, MisterSynergy: --Emu (talk) 12:30, 24 February 2023 (UTC)Reply

Seems pretty   Confirmed to me.--Jasper Deng (talk) 21:13, 28 February 2023 (UTC)Reply

26 February 2023

edit

Rationale, discussion and results

edit

Likely successor accounts to Humanisator after their “semi-retirement” @Kolja21, Epìdosis, MisterSynergy, Emu: --Emu (talk) 10:58, 26 February 2023 (UTC)Reply

28 February 2023

edit

Rationale, discussion and results

edit

Another likely successor account. @1997kB, BRPever, Jasper Deng, Sotiale, علاء: Could we have some indication whether you plan to follow up on this case? Or do you consider this to be outside of CU territory? I don’t want to be pushy but this is a user with a lot of potential to disrupt Wikidata. --Emu (talk) 15:57, 28 February 2023 (UTC)Reply

Effectively these users starting immediately to write to other users asking for confirmations or edits regarding authority IDs are quite suspect (e.g. recently also Salatalık Kral (talk • contribs • logs)). --Epìdosis 17:29, 28 February 2023 (UTC)Reply
That account is   Confirmed to the above three accounts.--Jasper Deng (talk) 21:17, 28 February 2023 (UTC)Reply


Comment

edit

@Kolja21, Epìdosis, MisterSynergy, Emu:

Werte Wikidata-Normdatler,

ich bin ein ehemaliges Mitglied der Redaktion Chemie der Wikipedia. Derzeit habe ich einen kaputten Knöchel und mache deswegen kurzweilige Wikidata-Edits.

Auf meiner früheren Arbeitsstelle sollte ich arbeiten und nicht Wikidata bearbeiten. Daher gewöhnte ich mir damals an, jeweils 50 (max. 65) Edits mit einem Wegwerf-Account zu tätigen und danach wieder ein neues Konto anzulegen. Es soll daher kein Geheimnis sein, dass ich

angelegt habe. Alle Konten haben dasselbe Passwort, das ich meinetwegen einem von euch mitteilen könnte.

Aus der Mehrzahl der Konten könnte man mir wohl einen Strick drehen: Ich weise darauf hin, dass sie konsekutiv aufeinander folgen und es keine zeitlichen Überschneidungen gibt. Ich logge mich üblicherweise nie wieder in alte Konten ein.

Über die Relevanz von Dingen (notability) kann man immer streiten, ich würde aber für jeden inhaltlichen Edit meine Hand ins Feuer legen.

Ich stelle gerne meine Telekom-Telefonnummer auf pastebin, lasse mich anrufen und kann dann beliebige mich verifizierende Edits von jedem dieser Konten tätigen.

PS: Bitte werft mich nicht mit dem Normdatentrolltroll zusammen. Ich habe mit jedem Konto z.B. Duplikate nach Property talk:P214/Duplicates/humans zusammengelegt. Ich hoffe sehr, dass ich dabei keinen einzigen Fehler gemacht habe. Falls doch, bitte mitteilen.

Bei Muḥammad Sallām Madkūr habe ich aufgrund der schwachen Datenlage nicht einfach zusammengelegt, sondern Kolja21, den ich schon oft als kurzen Dienstweg zur DNB benutzt habe (er möge mir das verzeihen), gefragt.

Bei nach DNB-Daten erstellten Datenobjekten von Russen oder Arabern fehlt oft der Name im Alphabet des Herkunftlands. Das korrigiere ich gerne. Beim Thailändischen fehlt mir die Fähigkeit dazu, sodass ich bei Sō̜nphachan Thavīkham peinlicherweise Google Translate benutzt habe. Habe ich sonst noch weitere Sünden begangen? Keines meiner Konten hat irgenwelche Debatten geführt wie der obige Troll.

CU-Hinweis: Ich editiere stets von einem Telekom-Heimanschluss im PLZ-Gebiet 38 aus.

Viele Grüße,

--Grifters gotta grift (talk) 16:55, 1 March 2023 (UTC)Reply

  Done blocked account for block evasion, implausible story --Emu (talk) 20:13, 1 March 2023 (UTC)Reply

15 March 2023

edit

Rationale, discussion and results

edit

Reason: Aligned with the new tactic of creating items (people, papers, organizations) in a niche. Still with a fixation on certain users, see User_talk:Kolja21#Johannes_Günther. See also Wikidata:Administrators'_noticeboard#Do_we_need_RFCU_for_clear_cases_of_sockpuppetry_(Tamawashi_cases) Emu (talk) 11:53, 15 March 2023 (UTC)Reply

  Comment Same behavoir by User:Ettiwdreg on German Wikipedia, see de:Benutzer Diskussion:Ettiwdreg#Altbekanntes Verhalten. --Kolja21 (talk) 22:03, 30 May 2023 (UTC)Reply
PS: He keeps deleting critical comments on his talk page. --Kolja21 (talk) 23:00, 30 May 2023 (UTC)Reply

Results: Unfortunately they are   Stale. In the future, having more evidence and archiving this page will help.--Jasper Deng (talk) 09:53, 4 July 2023 (UTC)Reply

09 August 2023

edit

Rationale, discussion and results

edit

Reason: Consistent with previous early editing choices: Interest in the Erik Amburger database ID (P6878), creation of (mostly unsourced) items about people from Prussia / Russia / Baltics. CC Kolja21. --Emu (talk) 13:28, 9 August 2023 (UTC)Reply

Results: Very   Likely them and thus blocked accordingly. As they are evading a global ban they should also be referred to m:SRG for a global lock.--Jasper Deng (talk) 09:00, 10 August 2023 (UTC)Reply

19 November 2023

edit

Reason:

  1. Field of work: check, GND and similar authority data
  2. technological skills: as always, Tobias shows quite some talent in his endeavours
  3. formatting quirks, inability to accept consensus against their own position and tendency to drift into pretty aggressive manners: Communication was okay for some time but the final stage has begun, endless discussions about each and everything while performing high-volume batch operations.

--Emu (talk) 23:27, 19 November 2023 (UTC)Reply

Yep, it's him (  Confirmed).--Jasper Deng (talk) 03:00, 14 December 2023 (UTC)Reply

2 December 2023

edit

Reason: Weird activity. Some activity in the Vodafone IP range (2A02:8108:50BF:C694:95E8:5F54:A208:E48D) is linked to this. Together with the rather high level of technical ingenuity, this leads to Tobias. CC Karl Oblique --Emu (talk) 20:32, 2 December 2023 (UTC)Reply

See also Wikidata:Requests for checkuser/Case/KunzLob954, sorry for duplicate. --Emu (talk) 20:34, 2 December 2023 (UTC)Reply
These three are   Confirmed to each other with no sleepers, but it's   Inconclusive as to whether they are related to Tobias. Considering the temporal proximity of a higher-confidence Tobias sock (Asterix2023, above), I'd say it's   Unlikely to be them.--Jasper Deng (talk) 03:07, 14 December 2023 (UTC)Reply

3 December 2023

edit

Reason: Another instance of weird discussion activity in connection with suspicious IP range. --Emu (talk) 22:11, 3 December 2023 (UTC)Reply

  Inconclusive as to relations to Tobias, but I found them   Confirmed to Jayden Gottwald (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · checkuser (log) · investigate).--Jasper Deng (talk) 03:08, 14 December 2023 (UTC)Reply

22 May 2024

edit

Rationale, discussion and results

edit

Reason:

- Nikki (talk) 16:27, 22 May 2024 (UTC)Reply

Results:   Likely them. Ranges are too busy to really look for sleepers.--Jasper Deng (talk) 00:30, 18 June 2024 (UTC)Reply

7 July 2024

edit

Rationale, discussion and results

edit

Reason: Main activity started in 21 June 2024 shortly after Elisabeth Pommern (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · checkuser (log) · investigate) was blocked. High technical knowledge, interest in Baltics-related people, mass creation of new items, propensity for endless discussions (e. g.Property talk:P227). CC Kolja21, Epìdosis --Emu (talk) 12:19, 7 July 2024 (UTC)Reply

Comments: The discussion on Property talk:P227 is not „endless“, but rather BergwachtBern (talk • contribs • logs) noting wrong links to geni.com (Q2621214). He is doing better work than the original editors of Baltisches biografisches Lexikon digital (Q18616550) – this is complex and highly valuable work!--Bernice Heiderman (talk) 13:29, 7 July 2024 (UTC)Reply


Results:

Selamiben

edit
Latest comment: 16 hours ago1 comment1 person in discussion

13 July 2024

edit

Rationale, discussion and results

edit

Reason: User:Deniz asked for rollback permissions only two days after another similar request was made by User:Selamiben and declined twice (!). Both users are from trwiki. The wording in the requests are also strikingly similar. User:Selamiben had a short block for socking on their turkish wikipedia which makes makes me think we should check for fowl play. User:Deniz also had a indef. block for socking on trwiki, but it was lifted almost immediately citing undisclosed evidence from VRT. Infrastruktur (talk) 09:31, 13 July 2024 (UTC)Reply

Results:

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