Wikipedia:Sockpuppet investigations/Laibwart/Archive

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Makes the same disruptive editings as User:Chickensire, User:Laibwart, IP 67.1.226.194, IP 65.129.128.18, IP 75.164.99.113 ZH8000 (talk) 07:47, 10 August 2016 (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

 * IP stale. -- Amanda  (aka DQ) 07:27, 13 August 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Makes the same disruptive editings as User:Chickensire, User:Laibwart, IP 67.1.226.194, IP 65.129.128.18, IP 75.164.99.113 ZH8000 (talk) 07:49, 10 August 2016 (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
IP blocked. Closing.--Bbb23 (talk) 16:49, 11 August 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Makes the same disruptive editings as User:Chickensire, User:Laibwart, IP 67.1.226.194, IP 65.129.128.18, IP 75.164.99.113, IP 67.1.47.34 ZH8000 (talk) 08:23, 10 August 2016 (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
IP is stale. Closing.--Bbb23 (talk) 13:40, 10 August 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Makes the same disruptive editings as User:Chickensire, User:Laibwart, IP 67.1.226.194, IP 65.129.128.18, IP 75.164.99.113, IP 67.1.46.81 ZH8000 (talk) 01:54, 15 August 2016 (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

 * IP now blocked. Closing. Bbb23 (talk) 15:05, 15 August 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Makes the same disruptive editings as User:Chickensire, User:Laibwart, IP 67.1.226.194, IP 65.129.128.18, IP 75.164.99.113, IP 67.1.46.81, IP 67.1.209.111, aIP 67.1.144.142 ZH8000 (talk) 00:53, 16 September 2016 (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

 * Admin action needed - . A short block on the IP (not more than a week) would be great. Kevin ( aka L235 ·&#32; t ·&#32; c) 02:11, 17 September 2016 (UTC)
 * Just a simple IP block for a short time, such as 1 week, does not help at all as the previous behavior of the very same user exemplifies. (S)he just gets another IP from the same network and goes on. IMO, it needs a better solution than a simple block of single IPs. -- ZH8000 (talk) 10:55, 17 September 2016 (UTC)
 * Blocked by for one week; closing.  If the behavior continues and you file another report, feel free to ping me and I will consider recommending a rangeblock. Thanks, Kevin ( aka L235 ·&#32; t ·&#32; c) 14:50, 17 September 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Again back, for the 10th time now!! Makes the same disruptive editings as User:Chickensire, User:Laibwart, IP 67.1.226.194, IP 65.129.128.18, IP 75.164.99.113, IP 67.1.46.81, IP 67.1.209.111, IP 67.1.144.14, 67.1.144.142.

All IPs are from the same network tcso.qwest.net from Tuscon, Arizona.

Blocking the IP for a certain time does obviously not change anything. I assume the person doing this has substantial mental problems. So we cannot expect that the usual means help to prevent any further disruptive editing.

Please provide better solutions. ZH8000 (talk) 22:16, 24 September 2016 (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
All old. Closing.--Bbb23 (talk) 00:50, 9 October 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

11th time: Makes the same disruptive editings as User:Chickensire, User:Laibwart, 67.1.226.194, 65.129.128.18, 75.164.99.113, 67.1.46.81, 67.1.209.111, 67.1.144.14, 67.1.144.142, 67.1.215.109. ZH8000 (talk) 08:27, 1 October 2016 (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

 * IP is stale, closing. GABgab 03:10, 14 October 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

12th time: Makes the same disruptive editings as User:Chickensire, User:Laibwart, 67.1.226.194, 65.129.128.18, 75.164.99.113, 67.1.46.81, 67.1.209.111, 67.1.144.14, 67.1.144.142, 67.1.215.109, 75.164.97.180. ZH8000 (talk) 17:29, 6 October 2016 (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

 * IP is now stale, closing. GABgab 23:57, 16 October 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Already back again, now for 13th time: Makings the same disruptive editings as User:Chickensire, User:Laibwart, 67.1.226.194, 65.129.128.18, 75.164.99.113, 67.1.46.81, 67.1.209.111, 67.1.144.14, 67.1.144.142, 67.1.215.109, 75.164.97.180, 65.129.195.249.

Dear admins, would you mind to check the past and find a more sustainable solution? ZH8000 (talk) 08:28, 19 October 2016 (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

 * closing because the IP is now stale. if you file again for this user, we need to see diffs showing how this user's edits are disruptive, and that show that the user you're reporting is making the same disruptive edits as past users. I could not tell just from looking at the IP's edits what was disruptive about their editing. Ivanvector (Talk/Edits) 19:51, 3 November 2016 (UTC)

Suspected sockpuppets



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

IP EDITS: 106.208 wikihounding, 136.109 adding unsourced info, 104.210 promoting David Duke 112.110 216.242 disruption & 216.242 on TripAdvisor & 216.242 removes word pub, 112.110 same edit as 216.242, 216.242 hounding SolarFlash

Socks: Winterduck adding unsourced claim, Dieterh making same edit as 216.242 Rockyhandsome100100's only edits were exact same as 216.242, and Iojhug contributes unsourced content.

The following IPs are stale: 67.1.105.169, 67.1.220.157, 67.1.210.62, 67.1.142.253 (edited Jeff Rense), 67.1.104.210 (Used once in 2008), 67.0.214.193 (this one I hate the most because it breaks the pattern), 67.1.106.208 (edited Jeff Rense to hound ), 67.1.136.109 (ed Jeff Rense), 67.1.144.142 (noted by to be evading block, 67.1.209.111,

The following have been blocked: 67.1.216.242 by after 's post to AN/I.

Sockmaster makes similar different disruptive edits to various articles within the same set, and also hounds users who revert them. Almost every single IP contribution on this list should be checked for accuracy. From what I can tell, it's the same Tucson, AZ network. Rangeblock should be a possibility. However, blocking 67.1.216.242/16 (what I calculated from just these IPs alone) might be a bit overboard.

I'd like to thank for all their hard work. I would not have found this long-term pattern of abuse without them laying the groundwork. &#8213; Matthew J. Long -Talk-☖  23:53, 4 February 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

67.1.112.110 showed up suddenly on Feb. 2 and 100% of the edits consisted of reverting my edits for a variety of bogus and misleading reasons such as "self promotion", "biased inuendo", and "vandalism and moral attacks upon subject". This editor seems to have a clear fascination with the Jeff Rense article, and indeed it was this edit (reverting a very contentious claim backed up by bogus citations) added much earlier by 67.1.139.227  (the same range in question) that seems to have triggered the wikihounding. This wikihounding is the subject of an open ANI that has already resulted in at least one IP being blocked.

After being warned to discontinue the disruptive behaviour, the editor seems to have switched to IP 67.1.216.242 (since blocked) to continue the same pattern of behaviour. I've identified a few accounts and IP addresses but I think MattLongCT's list if pretty comprehensive. SolarFlash (talk) 01:49, 5 February 2019 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
The two non-stale named accounts are ❌ to each other and, based on CU logs, unrelated to the master. With the exception of the recent IP, who is blocked, the edits of the other IPs and the one other named account are too old. Closing.--Bbb23 (talk) 01:11, 5 February 2019 (UTC)