Wikipedia:Sockpuppet investigations/FightOfTheLivingDeadFan/Archive

Suspected sockpuppets

 * ( original case name)


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

New user, same editing habits as recently blocked IP User: 47.146.89.139 RickyCourtney (talk) 22:55, 29 November 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Looks pretty clearly like a DUCK to me. Making the exact same edits to one of the same pages as the blocked IP editor. Trainsandotherthings (talk) 22:59, 29 November 2021 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * This looks pretty clear cut to me as well. Sir Sputnik (talk) 00:46, 30 November 2021 (UTC)

Suspected sockpuppets



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

Repeating edits by recently blocked IP 47.146.89.139 on Pacific Surfliner Pi.1415926535 (talk) 17:35, 30 November 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * The IP editor in question had a significant interest in Fight Of The Living Dead. Seems obvious to me. Also consistent with the sockmaster's poor spelling and grammar, and tendentious editing. Based on their unblock requests, which showed zero comprehension of the issues with their editing, they're likely to continue socking and page protection may ultimately be required. Trainsandotherthings (talk) 17:58, 30 November 2021 (UTC)
 * I literally just had to revert another disruptive edit from this user. Why have they not been indef'd yet? Trainsandotherthings (talk) 23:32, 6 December 2021 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * - to both IPs, and the IPs to . . Case moved from IP to oldest named account.  - for training. --Jack Frost (talk) 23:29, 30 November 2021 (UTC)
 * As above. - Please block  indefinitely, and 207.233.39.243 for a month. --Jack Frost (talk) 21:47, 3 December 2021 (UTC)
 * - I only see one edit on the IP that is clearly them, and it's from a week ago. Could you clarify why you are asking for a one-month block? Also noting that  is only blocked temporarily.  --Blablubbs (talk) 16:38, 6 December 2021 (UTC)
 * Given the scale of the disruption - two accounts and two IPs over 5 weeks - I think 1 month is too short, not too long. Judging by the unblock requests, this person has no comprehension why they've been blocked and will continue unless firmly blocked for a while. Pi.1415926535 (talk) 22:51, 6 December 2021 (UTC)


 * My thinking is that the IP is clearly them, pulling back to the /20 shows only this editor since 19 November, the IP / range is not highly dynamic looking at previous contributions, and it certainly doesn't look as if it will turn over to another user within the month, and they don't appear to have popped up on another address / range. Hence, a month seemed a nice round number to balance disruption of the target and minimising any collateral impact. Thanks, --Jack Frost (talk) 02:27, 8 December 2021 (UTC)
 * and are ✅ to each other. . Note I ran checks and blocked prior to realizing there was an SPI open.--  Jezebel's Ponyo bons mots 23:48, 6 December 2021 (UTC)
 * The user is already indeffed; the question here is whether blocking an IP would actually prevent them from continuing to edit – which I don't see as a given in this case. Looking at the entire /17, I only see one edit from over a week ago that is obviously them , with no indication that they are still on that IP or even still on that range. If they show up on the IP or the range again, we can reconsider IP blocks, but I don't see any clear indication that blocking now would be preventative. Closing. --Blablubbs (talk) 11:00, 8 December 2021 (UTC)

Suspected sockpuppets



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

Appeared at Coast Starlight just now to make the same edits as previous socks and the sockmaster. Geolocates to the same vicinity (Southern California) as previous IPs used by this sockmaster. Trainsandotherthings (talk) 22:41, 15 December 2021 (UTC)

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

47.146.89.128/26 is a possible rangeblock for this user. wizzito &#124;  say hello!  23:20, 15 December 2021 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Already blocked, closing. --Blablubbs (talk) 11:56, 16 December 2021 (UTC)

Suspected sockpuppets
Same habit of adding station lists and immediately self-reverting. IP geolocates to same area as past IP socks. Pi.1415926535 (talk) 22:13, 10 March 2022 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * About the most obvious IPsock ever. I also have experience with this particular sockmaster/LTA and it checks out. Trainsandotherthings (talk) 02:56, 11 March 2022 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Looks like them, blocking for a 3 months since they are still here with them being reported late November. Also noting that they've been spotted at recently which is in the same (big ISP) range as some of the previous socks. --Trialpears (talk) 15:27, 12 March 2022 (UTC)

Suspected sockpuppets
Here we go again.... user with the same habit of adding station lists and immediately self-reverting. --RickyCourtney (talk) 21:50, 18 March 2022 (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

 * based on behavioral evidence. Thanks for reporting this. —  Newslinger  talk   21:04, 19 March 2022 (UTC)

Suspected sockpuppets
Very loud quack: exact same pattern of messing with station lists. would be a likely rangeblock - a small amount of collateral damage, but hits a dozen or so different IPs used by this editor. >95% of edits from this range, dating back to 2017, are this editor. Pi.1415926535 (talk) 00:17, 27 September 2022 (UTC)


 * @Pi.1415926535 Oh, you mean train stations. At first I thought you meant radio stations and was thinking this was related to Sockpuppet investigations/85.5 FOR LA :-) -- RoySmith (talk) 01:37, 27 September 2022 (UTC)

Comments by other users

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


 * This is 100% the sockmaster editing via IP. They always geolocate to southern California and nobody else would do this behavior. Trainsandotherthings (talk) 21:52, 27 September 2022 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * /21 is a tad wide for my liking. blocked for 6 months. Closing. DatGuyTalkContribs 14:54, 28 September 2022 (UTC)

Suspected sockpuppets
Previously blocked sock has reappeared with the same pattern of unwanted changes to Amtrak station tables. Note that this IP has been the same sock since November 2021, so I request a block longer than the previous 3 months. Pi.1415926535 (talk) 23:05, 17 January 2023 (UTC)

Comments by other users

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


 * As someone who also has experience with this sockmaster, I fully endorse Pi's comments above. Trainsandotherthings (talk) 23:19, 17 January 2023 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked for 6 months. Closing. Callanecc (talk • contribs • logs) 09:18, 19 January 2023 (UTC)