Wikipedia:Sockpuppet investigations/Qais13/Archive

From Wikipedia, the free encyclopedia


Qais13

Qais13 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log· investigate · cuwiki)
05 November 2014[edit]
Suspected sockpuppets
  1. Similar edits, concentrating on the titles and styles of the Monegasque and Luxembourg royal families.
  2. As of this timestamp, Qais16 has only edited 51 articles,[1] 23 of which are the same as articles edited by Enredados.[2] This is a very high proportion of overlap. See, for example, Prince Felix of Bourbon-Parma: edited by IPs used by Guilherme Styles[3][4], Enredados[5] and Qais16[6]. DrKiernan (talk) 20:15, 5 November 2014 (UTC)[reply]

information Note: Maria Antoni and the IP are already blocked. DrKiernan (talk) 20:20, 5 November 2014 (UTC)[reply]

Comments by other users[edit]

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


Clerk, CheckUser, and/or patrolling admin comments[edit]

Qais16 blocked as a sock of Qais13 (talk · contribs). MSSourcer blocked as a sock of Qais16. There is some overlap between User:Enredados and the other accounts in terms of subject matter (e.g. honours of Luxembourg royalty) and articles (e.g. Heinrich XX, Prince Reuss of Greiz: edited by both Enredados and an IP used by Guilherme Styles, 189.248.48.191 (talk · contribs · WHOIS)). DrKiernan (talk) 23:17, 12 November 2014 (UTC)[reply]

Mrbluesz blocked as a sock of Qais16/Qais13. DrKiernan (talk) 22:00, 15 November 2014 (UTC)[reply]

  •  Clerk endorsed. If all of these accounts are the same person, then Enredados is the master as he predates Guilherme by two years. However, before moving this SPI to the "right" master and correcting any tags, a limited CU would be helpful (Maria and Guilherme are stale).--Bbb23 (talk) 16:48, 16 November 2014 (UTC)[reply]
  • Following are  Confirmed:
MSSourcer (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log· investigate · cuwiki)
Qais16 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log· investigate · cuwiki)
Mrbluesz (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log· investigate · cuwiki)
Enredados is no Declined as there hasn't been enough evidence presented. no No comment with respect to IP address(es) Callanecc (talkcontribslogs) 11:12, 17 November 2014 (UTC)[reply]
Just did some tagging. No action against Enredados. IP is stale.--Bbb23 (talk) 23:36, 17 November 2014 (UTC)[reply]

14 June 2015[edit]
Suspected sockpuppets

Edit-warring/block evasion to maintain article at Princess Sophie of Romania, previously targeted by socks Bluebosp (talk · contribs) and Updaterrr (talk · contribs). DrKiernan (talk) 20:04, 14 June 2015 (UTC)[reply]

Comments by other users[edit]

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


Clerk, CheckUser, and/or patrolling admin comments[edit]
  • @DrKiernan: I've declined the CU because you provide no reason why you requested it. As an aside, the puppet is older than the master.--Bbb23 (talk) 20:17, 14 June 2015 (UTC)[reply]
  •  Clerk note: @DrKiernan: In order to facilitate and expedite your request, please provide diffs to support your case. Please give two or more diffs meeting the following format:
  1. At least one diff is from the sockmaster (or an account already blocked as a confirmed sockpuppet of the sockmaster), showing the behaviour characteristic of the sockmaster.
  2. At least one diff per suspected sockpuppet, showing the suspected sockpuppet emulating the behaviour of the sockmaster given in the first diff.
  3. In situations where it is not immediately obvious from the diffs what the characteristic behaviour is, a short explanation must be provided. Around one sentence is enough for this. Vanjagenije (talk) 22:30, 14 June 2015 (UTC)[reply]
  • In view of the disruption caused by the filer, DrKiernan, I am closing this with no action, which seems to be what he wants anyway, although he's clearly going about it in an incomprehensible manner, particularly from an administrator.--Bbb23 (talk) 13:53, 15 June 2015 (UTC)[reply]

13 March 2016[edit]

Suspected sockpuppets

Qais13 edits primarily from a British Telefonica O2 network with an IP range of 82.132... (although he has also used 86.157.246.73 (talk · contribs · WHOIS) and 86.16.201.164 (talk · contribs · WHOIS)). Sockpuppet edit[7] near duplicated by new account[8] Same focus on Michael I[9][10][11] and Line of succession to the Romanian throne[12][13] DrKay (talk) 21:16, 13 March 2016 (UTC)[reply]

RoyalAlchemist focuses on the same narrow subset of articles, article sections and topics as Qais13 [14][15] and [16][17] and [18][19]. Note also use of the same blogspot sources, e.g. [20][21].

Comments by other users[edit]

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


Clerk, CheckUser, and/or patrolling admin comments[edit]

  •  Clerk note: - RoyalAlchemist is already blocked & tagged. I don't see the connection with Cacavela, it just looks like a Romanian user with an interest in this topic. Closing. Ivanvector 🍁 (talk) 00:58, 17 May 2016 (UTC)[reply]

03 April 2017[edit]

Suspected sockpuppets[edit]

Identical edits to previous sockpuppet IP that was blocked in December: e.g. [22][23] Celia Homeford (talk) 14:31, 3 April 2017 (UTC)[reply]

Comments by other users[edit]

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


Clerk, CheckUser, and/or patrolling admin comments[edit]


27 April 2017[edit]

Suspected sockpuppets[edit]

Same situation as Wikipedia:Sockpuppet investigations/Qais13/Archive#03 April 2017. Celia Homeford (talk) 13:56, 27 April 2017 (UTC)[reply]

Comments by other users[edit]

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


Clerk, CheckUser, and/or patrolling admin comments[edit]


20 September 2017[edit]

Suspected sockpuppets[edit]

These are all known blocked socks of Qais13, but given that we know he is sock-farming it might be worth checking for sleepers. DrKay (talk) 18:22, 20 September 2017 (UTC)[reply]

Comments by other users[edit]

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


Clerk, CheckUser, and/or patrolling admin comments[edit]

  •  Clerk endorsed - to confirm and check for sleepers. I see that the IP listed above is currently under a rangeblock that expires in five days. The block log shows multiple masters.
     — Berean Hunter (talk) 18:14, 25 September 2017 (UTC)[reply]
  • I would consider all of the above accounts to be  Confirmed socks. No sleepers as far as I can tell. There are a handful of unblocked IPs that made isolated edits, but not enough to block the underlying range which is otherwise very busy with constructive editing MusikAnimal talk 15:37, 27 September 2017 (UTC)[reply]
  • Accounts tagged, closing. GABgab 18:28, 27 September 2017 (UTC)[reply]

29 June 2020[edit]

Suspected sockpuppets[edit]

Same types of edits as Enredados to Geneva School of Diplomacy and International Relations (IP1, Enredados). Adds titles and styles to nobility pages with references to images or royalty forums. See recent reversions by 148.252.132.141 such as this on Romanian former royalty articles, similar to edits by Enredados. Edits same pages as several other socks such as Qais16 and MSSourcer. JoelleJay (talk) 23:17, 29 June 2020 (UTC)[reply]

According to the interaction timeline the user was switching between Enredados and 148.252.132.141 repeatedly on 6/28/20 (when the IP was making vandalism edits and edit-warring), and with 81.40.249.149 on a ton of articles in early June. There was also overlap with User:82.132.244.1 (8 days between edits on Alexander I of Yugoslavia, George V, Princess Elena of Romania, and Michael I of Romania). (talk) 16:20, 30 June 2020 (UTC)[reply]

I now see Enredados was never checkusered to confirm being a Qais13 sock, so I've struck my comments regarding them. I'll go back through and see if there is other evidence related to confirmed socks. Sorry for this disastrous SPI. — Preceding unsigned comment added by JoelleJay (talkcontribs)

Comments by other users[edit]

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

Clerk, CheckUser, and/or patrolling admin comments[edit]

  •  Clerk note: JoelleJay, since you've changed a few things since the original SPI was filed, could you please restate your concerns and evidence? GeneralNotability (talk) 18:42, 6 July 2020 (UTC)[reply]
  •  Clerk note: I notice that Enredados was first suspected of being a Qais13 sock way back in 2014. But, just like in 2014, having a shared interest in Luxembourg royalty isn't by itself enough to call somebody a sock, or even endorse for CU. -- RoySmith (talk) 23:39, 6 July 2020 (UTC)[reply]
  • No additional evidence provided, so closing. -- RoySmith (talk) 18:48, 18 July 2020 (UTC)[reply]

07 September 2022[edit]

Suspected sockpuppets[edit]

Restoration of an obscure article deleted after a deletion discussion[24][25][26][27]

Same IP range and topic area associated with Qais13 through evidence in other sockpuppet investigations. Celia Homeford (talk) 08:00, 7 September 2022 (UTC)[reply]

Comments by other users[edit]

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

Clerk, CheckUser, and/or patrolling admin comments[edit]

  • I'm not convinced that the named account is a sock - they seem to mostly edit about sports, while Qais13 & co. had a singular focus on royalty. It's not outside the realm of possibility that two different people might take an interest in this article. The IPs may have been socks, but they have not edited in years, so there's nothing to do with them now. Closing. Thanks, Spicy (talk) 00:42, 15 September 2022 (UTC)[reply]