Langbahn Team – Weltmeisterschaft

Wikipedia:Sockpuppet investigations/WhiteReaperPM/Archive


WhiteReaperPM

WhiteReaperPM (talk ·  · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log· investigate · cuwiki)

16 April 2024

Suspected sockpuppets

Created around the time when the original account was placed under scrutiny due to persistent copyright violations.

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


30 July 2024

Suspected sockpuppets

Ratnahastin (talk) 07:06, 30 July 2024 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
Chauthcollector (along with user DeccanFlood) is already filed under an SPI report at Wikipedia:Sockpuppet investigations/Koitot, and based off the general pro-Maratha editing tendencies of many of these sockfarms the user could fall under any of them as none of the presented evidence here is specific to WhiteReaperPM. Flemmish Nietzsche (talk) 07:17, 31 July 2024 (UTC)[reply]
Imperial Enjoyer is already filed under Wikipedia:Sockpuppet investigations/Historyenjoyer10. Flemmish Nietzsche (talk) 14:43, 18 September 2024 (UTC)[reply]

Clerk, CheckUser, and/or patrolling admin comments

  • Do not appear to be related either to each other or master.  Behavioural evidence needs evaluation. Izno (talk) 20:13, 27 September 2024 (UTC)[reply]
  • ShBi1902 looks to be unrelated to this mess, behaviorally speaking. Chauthcollector is definitely a sock, but looks closer to Koitot or R2dra. I'll note the results on the Koitot SPI.

30 August 2024

Suspected sockpuppets

The user GroovyGrinster is a very clear sockpuppet of WhiteReaperPM, there is very clear resemblance in their editing from the myriad of pages they have created being formatted the same, especially in citations which you will see for yourself when I provide the evidence below, but as well as them working on the same topics, primarily focusing on the Maratha Empire and making a large number of pages dedicated to the military history for their victories, or the Indian subcontinent in general.

Here's some of WhiteReaper's page creations: [18] [19] [20] [21] [22] [23] [24] [25]

These are some examples, now let's see the accused sockpuppet's pages, (groovygrinster).

[26] [27] [28] [29] [30] [31]

These are just a few examples and theres a myriad more which you can see off of their page creation list.

Forgive me if this is formatted oddly, this is my first SPI I've done in quite a long time, but I see very considerable evidence that this user is a sockpuppet, having identical citation and editing styles, as well as having edited on the same topic(s). Noorullah (talk) 16:39, 30 August 2024 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

The accused parties appear to be vote stacking on the Mughal dynasty talk page [32].

A couple of these are recent accounts, and it’s beginning to become obvious that these are socks. Hopefully a check user will get to the bottom of this soon. Someguywhosbored (talk) 2 September 2024 (UTC)

Pinging Ponyo, an Administrator who has dealt with this sockmaster before. @Ponyo: Noorullah (talk) 05:05, 7 September 2024 (UTC)[reply]

Most of the articles created by GroovyGrinster pertain to battles by the Maratha confederacy in which it emerged victorious. e.g:

They are engaging in the same POV pushing as the previous socks. Ratnahastin (talk) 17:04, 14 September 2024 (UTC)[reply]

@Liz: The editor in question is a block evader thus G5 is fully justified. Ratnahastin (talk) 06:56, 29 September 2024 (UTC)[reply]
Them being block evaders is not (technically) verified, so blocks for DE should not result in page deletions under G5; the pages should certainly be deleted, but the reason does matter. Flemmish Nietzsche (talk) 07:00, 29 September 2024 (UTC)[reply]
This was a sock block. The block for sock puppetry does not have to be verified by a CU. That's how G5 deletions are valid here. Ratnahastin (talk) 07:06, 29 September 2024 (UTC)[reply]
Indeed, it was a sock block, but asilvering's wording below implies that the blocks should have been for DE instead. Flemmish Nietzsche (talk) 07:13, 29 September 2024 (UTC)[reply]
To clarify, the reason I personally blocked those two accounts yesterday was because I wanted to stop the ongoing disruption, but that doesn't mean they're DE blocks and not sock blocks. I've just been very hesitant to use admin tools with respect to an SPI case since I don't have much previous non-admin experience with SPI in general and had been wanting to leave the actual administration here to The Pros. However, while I'm no SPI expert, after many hours of investigating this bunch I think I have somewhat unwillingly become a "Maratha battles source paraphrasing sockfarm" expert, and on that basis: yeah, these are sock blocks and block-evading deletions. -- asilvering (talk) 20:30, 29 September 2024 (UTC)[reply]
Okay but the block log makes it clear that the block concerns sock puppetry given all the evidence here. Ratnahastin (talk)
Block, please. This editor is continuing not only the pattern of Maratha-related POV-pushing but also the lifting of copyrighted material from Google Books and the Internet Archive with close paraphrasing. Compare the below.
Battle of Umrani created by WhiteReaperPM (I'd appreciate it if an administrator could compare the revision-deleted versions for this one):
Source Article
Pratap Rao magnanimously permitted the Muslim army to get out of this snare. This suicidal action naturally called forth a sharp censure from the Raja who ordered the general not be show his face to him till he had retrieved his lost prestige. Prataprao allowed Bhalol Khan to retire as he begged that he will never raise a war against Marathas. When Shivaji learnt about this he taunted Prataprao for making peace with enemy.
Peshwa's Expedition of Shrirangapattan created by Chauthcollector:
Source Article
Maratha ambitions in the Karnatak aimed mainly at the subjugation of the four Nawabs of Aurangzeb’s days, viz., those of Shira, Savanur, Karnool and Kadappa. The fifth, namely, the Nawab of Arcot was saved from Maratha aggression by his support from the British. Maratha ambitions in the Karnataka region primarily focused on subjugating the four Nawabs who had held sway since Aurangzeb's era: those of Shira, Savanur, Karnool, and Kadappa. The Nawab of Arcot, supported by the British, managed to evade Maratha advances.
Siege of Kondhana created by GroovyGrinster:
Source Article
No authentic source tells us how they managed to do so. However, the following account given by Khafi Khan, though undoubtedly imaginary, is plausible: The exact method of their entry is not clear from authentic sources, but Khafi Khan’s colorful account suggests a plausible scenario.
The raiding party then left the palace through a wicket gate in the backyard, joined the cavalry detachment that was left across the river and rode towards Karyat Maval collecting other cavalry detachments on the way.1532 They arrived safely at Sinhgad the next day. The raiding party escaped through a small gate, rejoined their cavalry, and reached Sinhgad the next day.
Jaswant Singh was encamped near Pune with his contingent and it was widely believed that the raid was carried out with his connivance.1 Jaswant Singh, who was camped near Pune, was suspected of having colluded in the raid
Shayista Khan did not remain for long in Pune. Frightened and mortified by this daring attempt on his life, he entrusted command of the army to Jaswant Singh and himself returned to Aurangabad.1540 Soon afterwards, at the beginning of May 1663, he was dismissed from the subadari of the Deccan and replaced by Prince Muhammad Muazzam, Shayista Khan, deeply shaken by the raid, relinquished command of the Deccan to Jaswant Singh and retreated to Aurangabad. By early May 1663, he was dismissed from his position and replaced by Prince Muhammad Muazzam.
I've analyzed several more articles by GroovyGrinster for close paraphrasing and tagged them for G12 deletion; you can see the list on their user talk page and I've included similar text comparisons on all of the associated article talk pages. (Courtesy ping for asilvering.) TechnoSquirrel69 (sigh) 17:08, 28 September 2024 (UTC)[reply]

I just nuked pages created by 103.120.60.34 (talk · contribs · WHOIS) and 103.120.60.57 (talk · contribs · WHOIS), which were moved into mainspace and edited by Imperial Enjoyer. It's giving... duck. A range block might be worth considering. plicit 14:16, 29 September 2024 (UTC)[reply]

@Explicit:, yes this range [37] has been evading block and adding unsourced POV content/copyvio to 100s of indian princely state stubs for months. And recently started mass additions of articles to a category [38],a range block is necessary to prevent disruption. Ratnahastin (talk) 14:28, 29 September 2024 (UTC)[reply]

Clerk, CheckUser, and/or patrolling admin comments

  • Does not appear to be related.  Behavioural evidence needs evaluation. Izno (talk) 20:13, 27 September 2024 (UTC)[reply]
    Thanks, I hate it. Chauthcollector, Imperial Enjoyer, GroovyGrinster all look extremely ducky to me but I don't want to make Baby's First SPI Block without backup from someone who knows what they're doing more than I do. -- asilvering (talk) 22:01, 27 September 2024 (UTC)[reply]
    Okay, nevermind. GG just sent a bunch more drafts to mainspace, after all of @TechnoSquirrel69's tagging things as CLOP copyvio yesterday, blocked the two active ones before they could do any more. Maybe it's meat, maybe it's socks, whatever it is, it's disruptive. -- asilvering (talk) 05:47, 29 September 2024 (UTC)[reply]
    Well, asilvering, it kind of does matter if you're deleting their work as CSD G5. That's reserved for editors evading a block, not for disruptive editors. Liz Read! Talk! 06:49, 29 September 2024 (UTC)[reply]
    Oh, I don't have any doubt they're evading a block. What I'm less sure about is whether the evasion is via sockpuppetry or meatpuppetry (which, as I understand it, makes no difference when it comes to G5), and how definitively Historyenjoyer10 can be identified as part of this same WhiteReaperPM circle. -- asilvering (talk) 07:50, 29 September 2024 (UTC)[reply]
  • This topic area is a mess with nests of socks fighting each other, but behaviorally GroovyGrinster has enough similarities with WhiteReaperPM to justify a block and tag.
information Administrator note Logging for future cases that there is good reason to believe several of the sockmasters involved here might be working together, or even run by the same person/group. Historyenjoyer10, Koitot and R2dra have a lot of overlap here but there are others that seem more distantly related. The WordsmithTalk to me 01:18, 9 October 2024 (UTC)[reply]
Yes, I agree that this is very likely. -- asilvering (talk) 05:34, 9 October 2024 (UTC)[reply]

31 October 2024

Suspected sockpuppets

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


20 December 2024

Suspected sockpuppets

Recreation of Battle of Umberkhind, previously G5'd. - UtherSRG (talk) 15:15, 20 December 2024 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
Hi admins, I am not an sockpuppet, I am ready to explain myself. This might be a mistake. PerspicazHistorian (talk) 16:04, 20 December 2024 (UTC)[reply]
How I got the content, Explanation: When i searched for "Batted of Umberkhind" , I got to know no such page exists. The I clicked "create page". I saw a warning sign that a draft exists. I clicked on it and used the source code to re-create the page. I was editing the page, then i got to know about the previous editor was a sockpuppet by this investigation by User:UtherSRG.
Please refer to the conversation: User talk:Girth Summit#Sockpuppet Investigation. PerspicazHistorian (talk) 16:41, 20 December 2024 (UTC)[reply]
That is not acceptable. Do not copy source from one place to another, as that breaks the attribution of the work. I have moved the article back to draft and merged the work together. I've left a warning on your talk page about this. - UtherSRG (talk) 22:06, 20 December 2024 (UTC)[reply]

Clerk, CheckUser, and/or patrolling admin comments