Wikipedia:Sockpuppet investigations/Conrailman4122/Archive

Suspected sockpuppets



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

The Editor Interaction Utility should speak for itself: Conrailman4122 (recently blocked 60 hours for edit warring / disruptive editing / personal attacks) is clearly using 67.87.196.115 for block evasion. Note the odd selection of common articles, and the tendency for occasional long angry edit summaries. Conrailman has clearly been using 67.87.196.115 (and earlier, 68.199.203.237) as an alternate for a while - see their identical edits 9 hours apart here, for example. There's also over a dozen currently-inactive 99.x.x.x IPs (all of which also geolocate to the NYC area) that I haven't listed here that have been doing the same edit warring on Amtrak paint schemes for months.

Based on edits at Ossining station - where 67.87.196.115 reverted my revert of 69.117.15.126 - and the geolocation to the same area, I believe it's possible that Conrailman/67.87.196.115 may also be related to a weeks-long pattern of disruptive IP edits, of which I've listed all the IPs that I'm aware of. Most or all are stale (most only edit for a few days), but I wanted to list them here for reference. Several are currently blocked after AIV reports: 69.117.12.248 was blocked by AGK, and 69.113.128.0/21 was blocked by Ferret. You can see the interaction for all the users here. There is limited article overlap with Conrailman/67.87.196.115, but some behavioral similarities. Pi.1415926535 (talk) 22:23, 11 October 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Clear block evasion here. Quacking into a megaphone. And continuing many days later. oknazevad (talk) 01:57, 19 October 2018 (UTC)
 * Agreed: clear block evasion which needs to be stopped ASAP. The user is causing disruption on multiple articles. –Daybeers (talk) 05:10, 21 October 2018 (UTC)
 * Further socking was carried out by IP Address 67.87.196.115 per these diffs, , . The edit summaries are also written in the same style as many of User:Conrailman4122, and this is both article, talk pages and edit summaries. Morphenniel (talk) 21:17, 1 November 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * The IPs listed above are all stale save for 67.87.196.115, which I will deal with in the report immediately following.-- Jezebel's Ponyo bons mots 23:54, 8 November 2018 (UTC)

Suspected sockpuppets



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

, and many, many more. This IP user is reverting edits by User:Cards8466 and on article that User:Conrailman4122 has edited or been associated with. I warned Conrailman4122 about sock-puppeting using this IP address per this diff. User:Conrailman4122 is evading a current two week block by editing using this IP address. Morphenniel (talk) 15:35, 7 November 2018 (UTC)

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

Alright, I do confess that this is my IP address behind my account. It was me and I deeply apologize for my actions. I was just trying to do helpful edits but it's just Pi.1415926535 who just comes in and reverts my edits on every article I encounter claiming they're "trivial" and "outsourced" and I got mad real easily and flipped out. I just couldn't stand Pi.1415 himself since he seemed to be "stalking" all the transport articles I visit and edit. And just simply rids the work and dedication I've done. He seems to not like my edits by modifying "Amtrak paint schemes" with a common name from a source. And to modify the less excessive use of images that describe each scheme. He keeps telling me he wants a source but for certain articles like "Amtrak paint schemes" and "GE Genesis" where I added true and supportive information and he says I need a source. I tell him why for the need of a source if I experienced and have personal knowledge with the locomotives. I tried to do my hardest to find a source but the guys on the article just discredited my source and reverted my edits. I was angry and flipped off giving up on them and my account was blocked thereafter. I understand I deserved the block from my account cause I knew my comments were rude and that I went out with my anger. It's just I cannot stand Pi.1415926535 and simply don't like him at all and would unleash my anger on him. He always wants trouble with me and it's just ridiculous. Again I apologize for the recklessness, disruption and evasions I've cause here. But I show no remorse for Pi.1415926535 as he has cause nothing but trouble with me for months but if he wants to talk with me that's fine. Otherwise I suggest not blocking my this IP address and will keep carrying out my block for two weeks. Mainly cause I've learned my lesson on how to be polite to others here. Afterwards I'll move on and try to control my temper and continue to contribute here on Wikipeida. 67.87.196.115 (talk) 01:31, 8 November 2018 (UTC)
 * I think the issue here is that you have failed to understand the purpose of the block. Block are imposed to deter disruptive editing and to encourage the editor to amend their behavior.  By using a sock-puppet (in this case using an IP address) to evade the block shows that you have failed to comprehend the reason why you were blocked.  Additionally, your editing using this IP address has also been disruptive and tendentious.  Morphenniel (talk) 12:00, 8 November 2018 (UTC)
 * And rants like this one, that has been redacted do not help your case. On the contrary this diff is the reason why you have been blocked, not only for using yet another IP account to evade the block, but abusive language too. Morphenniel (talk) 15:13, 8 November 2018 (UTC)
 * These diffs ,, from another IP address simply confirms that the Block was thoroughly justified.

Clerk, CheckUser, and/or patrolling admin comments

 * I've now blocked Conrailman4122 indefinitely for incessant disruption, block evasion and attacks. I've blocked IP 67.87.196.115 as it has been admitedly used for block evasion and made it clear that after this infantile outburst, Conrailman4122 is no longer welcome to edit Wikipedia under any account or IP.-- Jezebel's Ponyo bons mots 23:57, 8 November 2018 (UTC)
 * in this edit you changed the IP address in a closed SPI report and tacked on an additional report to the old one instead of opening a new report. I understand it was likely in error, but please don't ever modify reports this way again. In doing so, you made it appear that the IP I had blocked, 67.87.196.115, was admitting to also using the IP you added (IP 69.117.14.252), which resulted in me incorrectly blocking the new IP for admitted block evasion. If you want to add a new report, please follow the instructions under the "How to open an investigation" and ensure the report includes evidence in the form of diffs.-- Jezebel's Ponyo bons mots 20:02, 14 November 2018 (UTC)

Suspected sockpuppets



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

Clear and consistent pattern of behavior of unhelpful and non-consensus edits at New York/New Jersey/Philadelphia area rail articles as the master and previous IP socks, including being in the same range of IP addresses. For just a small sampling:, ,. Most have already been reverted, but nevertheless, the IP persists and reverts the reversions. oknazevad (talk) 20:26, 2 December 2018 (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 for a week. Closing/archiving. Courcelles (talk) 21:18, 2 December 2018 (UTC)

Suspected sockpuppets



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

A day after the last IP sock was blocked, immediately back to the same behavior with another close IP address. May need a range block here. oknazevad (talk) 01:42, 5 December 2018 (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 blocked the /21 for a two months. No comment on the technical aspects here, and I haven't looked, but there is enough behaviorally for a long range block. TonyBallioni (talk) 05:44, 5 December 2018 (UTC)

Suspected sockpuppets



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

Close IP to previous socking, and same sort of behavior as both the master and the previous socks of making non-consensus, MoS-ignoring edits to NYC-area commuter railroad stations and other related articles. See here for just the first example of many over the last few days. He can't seem to get it through his head that he's not welcome here because his edits constitute blathersome nonsense that is not even agreed to by anyone. oknazevad (talk) 16:32, 8 February 2019 (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

 * Obvious block evasion; IP blocked 1 week.-- Jezebel's Ponyo bons mots 21:07, 8 February 2019 (UTC)

Suspected sockpuppets



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

Same as before, edit-warring timetable info, see previous addresses.  Cards84664  (talk) 01:20, 6 July 2019 (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

 * WP:DUCK blocked for 31 hours per previous socks in archive. Closing. The SandDoctor  Talk 04:40, 8 July 2019 (UTC)

Suspected sockpuppets



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

Same pattern of error-introducing edits to NYC-area railroads that have previously been noted. Current IP is close in range to one previously blocked as a sock last week, so range block might be needed. oknazevad (talk) 03:02, 14 July 2019 (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

 * - Could we have another two month block on /21 please. &#8208;&#8208;1997kB (talk) 15:43, 15 July 2019 (UTC)
 * Range blocked. Closing. Reaper Eternal (talk) 15:54, 15 July 2019 (UTC)
 * Range blocked. Closing. Reaper Eternal (talk) 15:54, 15 July 2019 (UTC)