Wikipedia:Sockpuppet investigations/Aggiefan47/Archive

Suspected sockpuppets



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

User Aggiefan47 was blocked indefinitely on October 28, 2017. The ANI report can be found here. As a quick summary, Aggiefan was using their account disruptively more often than they were using it constructively, and they were completely unwilling to discuss or explain their edits despite several talk page requests to do so. Administrator A Train initially blocked Aggiefan indefinitely until they agreed to explain themselves and start using talk pages. Aggiefan removed these talk page notices and had their ability to edit their talk page removed, and it appeared to be over.

This morning (December 3) I noticed an edit to Carlos Beltrán which was instantly recognizable as something Aggiefan would have done. Reorganization of infobox fields (which have no effect on how the infobox is displayed), adding or removing spacing, moving medal templates outside of the infobox, and other minor/occasional parts of Aggiefan's edit pattern. In addition, the IP user explained themselves by leaving the following summary: "edited player biography, career highlights and awards and olympic information". This is a word-for-word copy of some of Aggiefan's edit summaries. They also edited Scott Diamond, Hal Woodeshick, Tyler Duffey, and Phil Hughes. After checking those edits it became very apparent to me that this IP was Aggiefan47. After I reverted the IP's edits, another IP, 2600:1700:45A0:A9E0:8577:C8CD:EC2B:3263, and made six additional edits (at the time of this posting) which are also very likely to be Aggiefan47 edits, based on their content and explanations. I have reverted those edits as well, and expect that Aggiefan will find another IP to continue disrupting WP:BASEBALL project pages. Trut-h-urts man (T • C) 19:22, 3 December 2017 (UTC)


 * Aggiefan47 has admitted using IPs to edit with this message on my talk page. Stating they are editing without logging into the Aggiefan47 account because it is blocked. Trut-h-urts man  (T • C) 18:57, 4 December 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Can we do a check for the edit summary "Edited player biography"? That could help us identify other IPs or accounts used. – Muboshgu (talk) 20:11, 3 December 2017 (UTC)
 * Here is another one. I was sure it was him but, not knowing that this had happened anywhere else, I didn't know if I had enough for an SPI. EricEnfermero (Talk) 18:05, 4 December 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
We don't publicly disclose the IP(s) of named accounts. CU declined.--Bbb23 (talk) 20:03, 3 December 2017 (UTC)
 * I guess I misunderstood the checkuser system. I never wanted Aggiefan47's IP released here. What I was hoping someone would do is check Aggiefan's IP to see whether the location of it is close/similar to the 2 other IPs I have reported, which would provide additional information to the investigation. My bad. Trut-h-urts man  (T • C) 20:09, 3 December 2017 (UTC)


 * The IP's are now stale. Closing. Sro23 (talk) 06:10, 16 December 2017 (UTC)
 * Are you sure about this? A block against the 2600:1700:45A0:A9E0:0:0:0:0/64 range seems like a viable option here, if this is all one person. Sir Sputnik (talk) 17:46, 16 December 2017 (UTC)
 * Please block the 2600:1700:45A0:A9E0:0:0:0:0/64 for a month, since it is clearly only being used by the same banned editor. Sro23 (talk) 21:16, 16 December 2017 (UTC)
 * . GABgab 00:34, 17 December 2017 (UTC)

Suspected sockpuppets



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

Note the same pattern of edits between this IP and the master at Paul Janish and the fact that the IP returned to edit Sid Gordon. EricEnfermero (Talk) 01:56, 8 December 2017 (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 IP is now too old to block. Sro23 (talk) 06:13, 16 December 2017 (UTC)

Suspected sockpuppets



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

This was yesterday, but same editing pattern. EricEnfermero (Talk) 02:02, 8 December 2017 (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

 * See above. Sro23 (talk) 06:13, 16 December 2017 (UTC)

Suspected sockpuppets



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

See George McQuinn for one example where Aggiefan47 edited the article in October and this IP did today. Same edit summary and mostly pointless messing around - adding spaces, taking out spaces, adding/removing piped links, etc. EricEnfermero (Talk) 22:23, 8 December 2017 (UTC)

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

Suspected sockpuppets



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

Another 2600.1700 IP with the same editing pattern. EricEnfermero (Talk) 15:33, 9 December 2017 (UTC)

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

Suspected sockpuppets



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

Another 2600.1700 IP with the same editing pattern. Trut-h-urts man (T • C) 22:39, 10 December 2017 (UTC)
 * I added another one. – Muboshgu (talk) 19:41, 11 December 2017 (UTC)

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

Suspected sockpuppets



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

More pointless tinkering and infobox rearranging in the usual pattern with the standard edit summary. Removed a GA icon from a GA. Pipes a link to runs batted in on one entry, takes out the same piped link in another entry minutes later. EricEnfermero (Talk) 23:49, 13 December 2017 (UTC)

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

Suspected sockpuppets



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

Another 2600.1700 IP with the same editing pattern. Trut-h-urts man (T • C) 04:38, 16 December 2017 (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

 * Stale IP. There's no need to open so many reports at once, next time simply add to the already opened case. Sro23 (talk) 06:13, 16 December 2017 (UTC)
 * Sorry about that. I was using Twinkle and I just thought that was how these were formatted. I'm assuming I should just add the IPs manually? Thanks for looking at this. EricEnfermero (Talk) 18:14, 16 December 2017 (UTC)

Suspected sockpuppets



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

The pointless infobox shifting has resumed after a quiet couple of weeks. EricEnfermero (Talk) 20:01, 3 January 2018 (UTC)
 * Sorry, I was intending to connect this to User:Aggiefan47, as this seems to be another attempt at block evasion. An IP address range block worked well at first. EricEnfermero (Talk) 20:03, 3 January 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

 * . GABgab 02:33, 4 January 2018 (UTC)

Suspected sockpuppets



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

Same infobox tinkering with pointless edit summaries - caps fixes to templates, unnecessary spacing edits. EricEnfermero (Talk) 02:03, 5 January 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

 * . GABgab 03:09, 5 January 2018 (UTC)

Suspected sockpuppets



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

Same pattern of infobox rearranging, block evading. EricEnfermero (Talk) 23:22, 5 January 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

 * . GABgab 00:07, 6 January 2018 (UTC)

Suspected sockpuppets



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

EricEnfermero (Talk) 03:11, 20 February 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

 * . GABgab 03:27, 20 February 2018 (UTC)

Suspected sockpuppets



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

Based on the following edits:, , , , , , , , , and. These edits show several aspects of Aggiefan47's edit pattern, including pointless re-ordering of infobox fields, capitalizing the "b" in birth date and age templates, inserting or removing infobox field spacing, and an irrelevant (and outright false) edit summary. Trut-h-urts man (T • C) 16:19, 22 March 2018 (UTC)


 * I have added IP 98.200.13.180 to the report (based on these edits:, , , , , , , , , , , , and ). Trut-h-urts man  (T • C) 16:26, 23 March 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 edits are too old. Closing. Bbb23 (talk) 11:10, 2 April 2018 (UTC)

Suspected sockpuppets



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

Based on pretty much the entire edit history, but specifically the following edits:, , , , , , , , , , , , , , , , and .These edits show several aspects of Aggiefan47's established edit pattern, including but not limited to pointless re-ordering of infobox fields, capitalizing the "b" in birth date and age templates, inserting or removing infobox field spacing, and an irrelevant (and/or outright false) edit summary.

I'd also like to ask the administrator who responds to this investigation to consider a range block, as the IPs I reported last week for also being likely socks (98.200.14.37 and 98.200.13.180) are very close to this new IP, as well as a handful of earlier-reported IPs. A different range block is already in place for Aggiefan (2600:1700:45A0:A9E0:0:0:0:0/64). Trut-h-urts man (T • C) 23:31, 8 April 2018 (UTC)


 * I have added additional IP addresses, gathered from the 98.200.13.0/24 and 98.200.14.0/24 IP ranges, to the report. Evidence for each reported IP is listed beside.
 * 98.200.13.216 -, , , , , , , , , , , , and.
 * 98.200.13.113 -, , , , , , , , and.
 * 98.200.13.225 -, , , , , , , and.
 * 98.200.13.168 - and
 * 98.200.13.86 - and
 * 98.200.13.226 -, , , , , , , and
 * 98.200.14.87 -, , , , , , , and
 * 98.200.14.94 -, , , , , , , and
 * 98.200.14.119 -, , , , and
 * 98.200.14.20 - and
 * 98.200.14.101 - and
 * 98.200.14.162 - and
 * 98.200.13.180 (reported here on March 23 - declined as stale) -, , , , , , , , , , , , and
 * 98.200.14.37 (reported here on March 23 - declined as stale) -, , , , , , , , , and


 * Due to this overwhelming evidence, I believe range blocks are warranted. I have also included the IPs I reported on March 23 as further support for range blocking. Trut-h-urts man  (T • C) 01:49, 9 April 2018 (UTC)


 * Added 98.200.13.158 (evidence:, , and ) Trut-h-urts man  (T • C) 02:29, 10 April 2018 (UTC)
 * And another one (98.200.14.67 - evidence:, , , , and ). Should be clear by now that Aggiefan has no intention of stopping his continued disruptions to WP:BASEBALL. Trut-h-urts man  (T • C) 19:05, 10 April 2018 (UTC)
 * A new one every day. 98.200.14.3 evidence:, , , , , and . Trut-h-urts man  (T • C) 20:45, 11 April 2018 (UTC)
 * 98.200.14.62 added (,, , , , , and ) Trut-h-urts man  (T • C) 15:43, 12 April 2018 (UTC)
 * I have added yet another IP to the report. 98.200.14.103 (evidence:, , , , , , , , , , , , , and .) There's more but I think that's enough for now. Trut-h-urts man  (T • C) 19:45, 13 April 2018 (UTC)
 * Two more. 98.200.14.149 and 98.200.14.118. Trut-h-urts man  (T • C) 16:33, 15 April 2018 (UTC)
 * 98.200.14.27 added. Trut-h-urts man  (T • C) 20:27, 16 April 2018 (UTC)
 * A bunch more added. Trut-h-urts man  (T • C) 15:33, 30 April 2018 (UTC)

Adding one: EricEnfermero (Talk) 23:45, 9 May 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * I just accidentally filed one under Aggiefan22 (not sure what I was thinking), but it’s the same 98.200... range that has been particularly problematic in the past. EricEnfermero (Talk) 00:18, 12 April 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
IP edits too old. Closing.--Bbb23 (talk) 13:13, 11 June 2018 (UTC)

Suspected sockpuppets



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

EricEnfermero (Talk) 16:46, 27 April 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 edits too old. Closing.--Bbb23 (talk) 21:10, 11 May 2018 (UTC)

Suspected sockpuppets



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

After having received some advice from User:Bbb23 I am re-opening this investigation and listing just the two IP ranges Aggiefan47 has been abusing to disrupt WP:BASEBALL project pages almost daily. Having observed these ranges for more than the past two months, it is my belief that, aside from this lone edit, the only person using these ranges is Aggiefan47. It is also my opinion that Aggiefan has no intention of stopping (and has already caused one IP range to be blocked). For some background on Aggiefan47's history of disruptive activity, see this archived block discussion. To summarize, Aggiefan47 regularly reorganizes infobox fields (which has no effect on how they are displayed) or completely removes them, adds or removes infobox spacing, changes lower-case letters to upper-case (again with no actual effect), introduces grammatical and spelling errors, removes statistical information from infoboxes, and numerous other minor disruptions. There is very little consistency to their edits, as one moment they will remove something from a page and, in their next edit, add it to another. It was the consensus of several WP:BASEBALL editors and Wikipedia administrators that Aggiefan's lack of helpful edits and unwillingness to collaborate meant that they should be blocked indefinitely. As well, Aggiefan openly admitted on my talk page that they were using IP addresses to continue editing Wikipedia. Trut-h-urts man (T • C) 00:29, 12 June 2018 (UTC)


 * I have added the 98.200.15.0/24 range to the report, as Aggiefan is into that one now. Trut-h-urts man  (T • C) 13:15, 2 August 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * I would endorse a three or six month soft rangeblock on both ranges; the last 500 edits on each range appears to entirely consist of garbage from this person. The range belongs to Xfinity Wifi in the Houston, Texas area, a service which anyone close enough to a Comcast modem can connect into. Based on the geographic location, and the cryptic nature of the disruption, I half way wonder if this is a return of Mmbabies with a new twist. PCHS-NJROTC  (Messages)Have a blessed day. 03:28, 14 June 2018 (UTC)
 * (Just to demonstrate how Xfinity WiFi works, except this one geolocates to Sarasota, Florida despite me actually be located in Port Charlotte, Florida; the geolocation isn't exact with this service. I have never been a Comcast customer, but my next door neighbor is and I can access it from their modem. I don't know if that's just a Florida thing or if they have that set up nationwide now, but even before they opened them all one had to do was use a Mailinator account and get unlimited free 30 minute sessions). 73.91.1.1 (talk) 03:39, 14 June 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * - Pending technical questions. Sir Sputnik (talk) 04:45, 19 August 2018 (UTC)
 * WP:DUCKs, blocked ranges for 3 mos each. Biggest risk is WP:CTDAPE with mass edits without discussing concerns of community. Potential for collateral damage appears minimal, and is likely a public wifi connection.—Bagumba (talk) 09:57, 22 August 2018 (UTC)
 * Thank you . Archiving. Mkdw  talk 21:00, 24 August 2018 (UTC)

Suspected sockpuppets



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

Continuation of long-standing block evasion efforts, this time from a registered account rather than from constantly changing IPs. The main feature is baseball infobox editing that results in a) no change to the text, or b) an error. Examples: Capitalizing the B in the ‘Birth date and age’ template, adding piped links to cities or statistics in order to avoid redirects (WP:NOTBROKEN). Larry Hockett (Talk) 22:52, 1 December 2019 (UTC)

In response to the reminder below, I'm adding some diffs. Both accounts almost exclusively edit the infoboxes or leads of baseball player entries. The problematic edits largely fall into one of a few categories. I'm trying to provide at least one example from each account, but for some of these issues, there are hundreds of examples.


 * Unhelpful edits to indefinite articles in the first paragraph of the lead.
 * Aggiefan47:
 * Astrosfan20177 - from tonight alone:


 * Changing the capitalization of the BDA/DDA infobox templates
 * Aggiefan47:
 * Astrosfan20177:
 * Astrosfan47 (short-lived sock):


 * Adding (or occasionally removing) the piped link to run batted in (or other terms) unnecessarily
 * Aggiefan47:
 * Astrosfan20177:

Essentially, this editor comes across as careless and just WP:NOTHERE, and he seems to prefer block evasion to discussion.

Hope this helps. Larry Hockett (Talk) 07:41, 5 December 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 you provide some specific diffs that demonstrate the socking behavior? -- RoySmith (talk) 22:23, 4 December 2019 (UTC)
 * Thanks for the diffs. Blocked and tagged.  -- RoySmith (talk) 15:51, 5 December 2019 (UTC)

Suspected sockpuppets



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

Reported at WP:AIV in Special:Diff/931475127 by Larry Hockett. Compare username and edit summary style to Special:Contributions/Astrosfan20177, especially at the bottom of both users' contribution lists. ~ ToBeFree (talk) 03:25, 19 December 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

 * , closing ~ ToBeFree (talk) 03:32, 19 December 2019 (UTC)

Suspected sockpuppets



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

Obvious block evasion. See edits like this - pointless infobox edits, such as changing from lowercase to uppercase template names. Recently blocked usernames include Astrosfan20177 and Astrosfan20199. Larry Hockett (Talk) 00:01, 20 December 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

 * ✅ plus . ST47 (talk) 08:27, 20 December 2019 (UTC)

Suspected sockpuppets



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

More iterations of Aggiefan or Astrosfan with the typical pointless infobox edits, as here - changing the case of non-case-sensitive templates and moving around parameters that the infobox is going to put into its own order anyway. Larry Hockett (Talk) 01:28, 27 January 2020 (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. Closing. Tagged, as well as tagging master. Dreamy Jazz 🎷 talk to me &#124; my contributions 01:48, 27 January 2020 (UTC)

Suspected sockpuppets



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

Aggiefan47 has returned to editing pages using the above IP ranges (which were each previously blocked through these investigations), as evidenced through their edit pattern of making inconsequential changes to baseball player infoboxes, including adding px after image sizes, making minor spacing adjustments to infoboxes, changing infobox parameters to avoid redirects, capitalizing the "b" in the birth date template, reorganizing infobox parameters, and separating medal templates from infoboxes. They are also displaying their usual inconsistencies, as the final edit in the preceding evidence removes the "run batted in" redirect while the third cited edit adds it. Trut-h-urts man (T • C) 02:06, 27 May 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.'' Yes, these edits waste a lot of time sorting through the null edits to find the errors he introduces. I’ve noticed several 98.200 IPs doing this recently (pandemic boredom?) but haven't taken them here because he usually stops after a few edits. I think range blocks have been temporarily effective in the past. I noticed IP at this today. See User talk:2601:2C7:8100:62E0:D4A0:6C88:9882:8B05. Not an IP I would associate with this user, but it's WP:DUCK. Larry Hockett (Talk) 02:29, 27 May 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
I've anon-only rangeblocked the two ranges for 6 months again; the only potential collateral damage on them seems to be occasional other completely unconstructive editors.

, I agree that IP address is certainly the same editor - in fact they randomly seem to have been using that IP for about half an hour before switching back into the 98.200.14.0 range with no gap. I've put a shorter block on that address, but please do report if you spot more edits from that kind of IP. ~ mazca  talk 14:42, 27 May 2020 (UTC)

Suspected sockpuppets



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

2600:1700:45A0:9040:18CC:36CF:E296:58F3 reported to AIV by, checked the /64 and it's clearly the same pattern of edits that Aggiefan47's been doing intermittently for a while - unhelpful null edits and infobox rearrangements over a few weeks with various IPs within that range. Geolocates to the same place as usual. ~ mazca  talk 21:53, 3 September 2020 (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
Rangeblocked the IP /64, no further action necessary that I can see - reporting pro-forma to make sure it's clear this user is still active. ~ mazca  talk 21:53, 3 September 2020 (UTC)

Suspected sockpuppets



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

A WP:DUCK. – Muboshgu (talk) 00:34, 22 December 2020 (UTC)


 * , both of this accounts mainspace edits are edits to infoboxes of baseball biographies, similar to edits made by the sockmaster and socks in that there is unnecessary captalization changes to "Birth" and unpiping of Runs batted in Also note the lack of creativity in username. – Muboshgu (talk) 01:07, 22 December 2020 (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

 * -- RoySmith (talk) 00:54, 22 December 2020 (UTC)


 * -- RoySmith (talk) 01:26, 22 December 2020 (UTC)

Suspected sockpuppets



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

Aggiefan47 usually stops evading his block after a few edits and a UTP warning, but recently he's editing in multiple spurts per day and needs some assistance to stop.

There are multiple IPs involved, but it's all the usual things: pointless infobox tinkering such as changing the case on the BDA and DDA templates, reordering infobox parameters and adding spaces after asterisks whether or not there are spaces already, and messing with piped links even though he will eventually get bored and change the piping again.

Some of these IP addresses have been quiet for a few days. I'm just including them here in case it helps to locate a potential range block. I don't know much about how that works. Thanks. Larry Hockett (Talk) 02:29, 7 July 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

 * For those of you not familiar with US universities, An "Aggie" is somebody who goes to Texas A & M (and particularly a member of one of their sports teams). 98.200.12.0/22 and 2601:2C7:8100:62E0::/64 both geolocate to (surprise, surprise) Houston, Texas.  Both of these ranges have been mentioned in the archives multiple times, with blocks of various lengths.  I don't see any non-aggiefan traffic on either range, so I'm going to softblock both for some substantial amount of time. -- RoySmith (talk) 15:42, 17 July 2021 (UTC)

Suspected sockpuppets



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

Same stuff as before - this edit has the main features of Aggiefan47 - adding and removing piped links unnecessarily, changing birth/death parameters, tinkering with Olympic parameters. Note that this IP’s first edits were related to the Texas A&M Aggies. Larry Hockett (Talk) 14:11, 11 October 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

 * IP has been blocked for a month by HJ Mitchell. Closing case. Thanks, Spicy (talk) 06:23, 12 October 2021 (UTC)

Suspected sockpuppets



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

Still using baseball infoboxes as playtime, still geolocates to Houston. A hefty dose of null edits and block evasion, with a side of out-and-out mistakes. The infobox template specifically states that MLB and NPB stats are both supported, but Aggiefan47 has been on a longtime quest to remove the NPB stats. Larry Hockett (Talk) 14:22, 6 December 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

 * IP blocked by HJ Mitchell, closing. Thanks, Spicy (talk) 07:00, 7 December 2021 (UTC)

Suspected sockpuppets
Follows similar edits such as moving medal templates and capitalizing the b in birth date and age. I’m new to this so if there’s anything wrong with this report please let me know. Aaron Liu (talk) 17:16, 13 January 2023 (UTC)
 * Some evidence of Aggiefan's edit patterns      Trut-h-urts man  (T • C) 17:20, 13 January 2023 (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 3 months - topic area, tell-tale signs and geolocation match. Closing. Callanecc (talk • contribs • logs) 06:58, 14 January 2023 (UTC)

Suspected sockpuppets
Another probable Aggiefan sock. Edits in line with pattern, including meaningless infobox field reordering, addition of random spaces, etc., , , ,  Trut-h-urts man  (T • C) 18:29, 24 January 2023 (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 hasn't edited in a few days. Closing. Bbb23 (talk) 16:21, 27 January 2023 (UTC)

Suspected sockpuppets
He's baaaack. Last block of this IP, earlier this year for block evasion, was for three months. Many of the same issues - nuisance null edits like capitalizing the B in the BDA template or rearranging the order of infobox parameters. Edited to add: I think I messed up and listed Aggiefan47 as a sockpuppet rather than a sockpuppeteer. Should I refile this? Larry Hockett (Talk) 00:35, 3 June 2023 (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

 * - Please move to Sockpuppet investigations/Aggiefan47. Bbb23 (talk) 13:16, 3 June 2023 (UTC)
 * Done. Spicy (talk) 22:06, 5 June 2023 (UTC)
 * Blocked the IP for a long time. Closing. Thanks, Spicy (talk) 16:18, 5 July 2023 (UTC)