Wikipedia:Sockpuppet investigations/Exilvm/Archive

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

They were edit warring to revert to their poorly sourced POV version while logged out despite having an account when their disruption caused the page to be semi protected they logged into their account to continue the war,when protection expired they have started IP socking again. , Ratnahastin  (talk)  09:46, 22 August 2021 (UTC)


 * They are back again,when I reverted them for apparent Sockpuppetry they have reverted me   Ratnahastin  (talk)  09:07, 23 August 2021 (UTC)

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

 * I left them uw-login. Hopefully that'll be the end of it.  If not, please file a new report. -- RoySmith (talk) 18:50, 1 September 2021 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

warned this user against IP socking last time and it is continuing. I would recommend indef block as the user is WP:NOTHERE and hates to hear what others tell him. TolWol56 (talk) 13:35, 18 September 2021 (UTC)

I was talking about blocking the account Exilvm. TolWol56 (talk) 14:05, 18 September 2021 (UTC)


 * Well, Exilvm hasn't edited for a month (except their own talk page), and the protection on Umm Qirfa should prevent any further disruption from the IPs on that page.  The goal of blocking and page protection is to prevent ongoing disruption, and we've done that.  If Exilvm starts editing again, we can always take another look at that time. -- RoySmith (talk) 14:16, 18 September 2021 (UTC)

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

 * The page has already been protected. Blocking 92.40.187.0/24 would cover all the IPs in this case, but it looks like there's other legitimate activity there, so I'll hold off on that for now.  Closing. -- RoySmith (talk) 13:48, 18 September 2021 (UTC)