Home • Search • Translate
From Wikipedia, the free encyclopedia


Andrew5

Andrew5 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)

03 September 2019

Suspected sockpuppets

Self-admitted and behaviorally similar. Jasper Deng (talk) 20:57, 3 September 2019 (UTC) reply

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

Blocked, tagged, closing.-- Bbb23 ( talk) 21:54, 3 September 2019 (UTC) reply

26 December 2020

Suspected sockpuppets

See below. TonyBallioni ( talk) 13:09, 26 December 2020 (UTC) reply

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

28 December 2020

Suspected sockpuppets

HurricaneTracker and HurricanEdgar had both edited weather related articles, both have similar names, and Edgar has decided to edit Trackers talkpage [1] [2] [3]. Obvious sock is obvious. Thanks. – Davey2010 Talk 11:45, 28 December 2020 (UTC) reply

Comments by other users

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

Cabayi - Ah okay fair point, In this case I may of put 2+2 together and came up with 5. The name, edit area and editing HTs talkpage raised eyebrows but ofcourse I may be completely wrong (which if I am then my apologies). Thanks, – Davey2010 Talk 13:11, 28 December 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  •  Clerk note: I don't find this plausible since TonyBallioni conducted a CU just two days ago and didn't make any comment on this user. Given their shared area of interest it isn't that unusual that Edgar might notice the block & make some edits to Tracker's usertalk. I'll pause before closing in case Tony wants to tell us I'm wrong. Cabayi ( talk) 12:21, 28 December 2020 (UTC) reply
  • Yeah, while it’s not always the case that we get everything in CU, this would have shown up and it didn’t. Closing. TonyBallioni ( talk) 14:26, 28 December 2020 (UTC) reply

28 December 2020

Suspected sockpuppets

User:Andrew5 sockpuppets used this IP to sock and for meatpuppetry ~ Destroyer 🌀 🌀 18:26, 28 December 2020 (UTC) reply

Comments by other users

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

I added more IPs that have been recently abused, within the past month. As well as a range with a history of CU blocks. They are all behaviorally identical, per WP:DUCK. We don't need a CheckUser to publicly link the IPs to the sockmaster, given the obvious behavioral connections. However, given Andrew's history of deception and socking, I would like to request a CU to run a sleeper check on all of the IPs for any new accounts. And any IPs that have been abused by this LTA within the past month should probably be (re)blocked as well. LightandDark2000 🌀 ( talk) 21:15, 28 December 2020 (UTC) reply

Here is some specific evidence pertaining to the remaining IPs that have yet to be blocked: [4] [5]. Here is a confession of sorts (upon closer examination, especially in light of the off-wiki email from Gale5050 to another Wikipedia user on Uncyclopedia, I believe that Andrew was lying and that it was actual socking, not Meatpuppetry). And the block log of the listed /24 range proves the connection to Andrew5. Additionally, a closer look at any edits from any of the IPs on tropical cyclone and highway articles (or any topics in which the socks have overlapping interests) will reveal that they are all essentially the same person. Especially on discussions. Their editing patterns, mannerisms (including difficulty grasping WP policies), and lines of reasoning are all identical. LightandDark2000 🌀 ( talk) 23:49, 29 December 2020 (UTC) reply
I have communicated with Andrew5 on e-mail yesterday and he requested me to show his side of the story in User talk:HurricaneTracker495. But since the page is fully protected, and I did not want to go into trouble trying to get that page edited, I decided to show it here.

I’ll tell you what really happened. My friend, gale5050/Andrew5, told me to do some vandalism on Wikipedia, which I did here. Then they slowly began to get me more into Wikipedia at school which I evantually did, some of my edits were meatpuppety edits but I am a meatpuppet only. I am however, block evading as 2600:387:5:800::/60.

I shouldn’t, but admittedly, we’re both a little hotheaded, meaning we don’t always think before we act. Besides, gale5050 was a very close friend, and in March I was thinking “hey, let’s deface a users talk page!”. I don’t think that way anymore, I’ve matured since, but there is a lot I didn’t know. For example, while I knew they abused wiki data, I was not aware of this blatant harassment. Still, I will agree they have influenced me to (1) make poor decisions and (2) to make me vandalize articles a few times.

In correspondence with him, I'm trying to push him to stop his antics and take a six months away from Wikipedia (to be eligible for taking a standard offer), thus he confessed to me about his actions. Though, it is likely that he's lying to me (based on the his history of lying and deception) about meatpuppetry given he has a control of Gale5050 account on Uncyclopedia. If he's caught sockpuppeting again around this period of time between January to July 2021, I will have a long-term abuse page ready. SMB9 9thx my edits! 00:45, 30 December 2020 (UTC) reply
@ MarioJump83: Gale5050/Andrew5 emailed me on Uncyclopedia, explaining that he was HT495, and in his message welcoming me, he said that he was “that blocked sock”. -Shift 674- 🌀 contribs 20:38, 21 January 2021 (UTC) reply
Gale5050 has been disruptive on Uncyclopedia as well, and his editing is being restricted. Not going into too much detail but many issues (e.g. lying, circumventing blocks/sanctions) have cropped up on Uncyc too. Hipponias ( talk) 11:15, 24 March 2021 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  •  Check declined by a checkuser - I've already looked at all the ranges that the most recent sock was editing on (note; no comment as to if any of the above are them.) Cabayi, mind looking at these for the possibility of blocks? Use your judgement, etc. TonyBallioni ( talk) 01:51, 29 December 2020 (UTC) reply
  •  Clerk note: I can see 67.x is a sock, Special:Diff/993860667, and have blocked for 2 months. Destroyeraa & LightandDark2000, you've obviously seen some evidence - don't be coy, present it. " The truth is out there" isn't enough. Or is it just a shared interest in tropical storms and interstates? Cabayi ( talk) 22:41, 29 December 2020 (UTC) reply
  • A few things. General comment to everyone: this isn't meatpuppetry. Assume good faith isn't a suicide pact so let's not pretend it is here by feeling bad for someone who is lying to us. In cases where there are shared IPs and the like, behavioural analysis matters, and this is very clearly the same person.
    SMB99thx: please don't create an LTA page. They stick out like a sore thumb once you've dealt with them, and the CU log is detailed enough that an open record like an LTA page isn't needed. This SPI should be sufficient for people to report and document, and it's already more active than I would have suspected.
    Destroyeraa: minor procedural note, but typically at SPI, if you're not an admin, clerk, or CheckUser, you comment in the section above and ping clerks/admins/CUs in this section in response, rather than replying directly in the threaded discussion. Not a big deal, but thought I'd let you know for future reference.
    With that, back to Cabayi. TonyBallioni ( talk) 05:55, 30 December 2020 (UTC) reply
  • The remaining IPs are very lightly used in comparison to the 67.x IP. Any further blocks would be punitive rather than preventative. Also, the 170.24.150.0/24 range is held by Nassau County Board of Cooperative Education Services, and cutting off 56 school districts for one infrequent sock is way too much collateral damage. Closing. Cabayi ( talk) 18:21, 31 December 2020 (UTC) reply

28 September 2021

Suspected sockpuppets


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

23 February 2022

Suspected sockpuppets

  Looks like a duck to me Obvious block evasion by the LTA Andrew5. The behavior and areas of interest of these IP socks are identical to those of other IP socks that were blocked earlier this month, such as 69.118.232.58 and 108.170.65.170. This person is editing on the same articles/talk pages as earlier IP socks, as well as similar ones. The articles targeted are all weather articles, especially severe weather/non-tropical storm articles, which he has been very active on in recent months. The similarities include: large-scale intra-wiki copying [6] [7] [8] [9], spamming (often frivolous) renaming requests [10] [11] [12], numerous AfD requests or commenting at said pages (including activity at Wikipedia talk:Articles for deletion) [13] [14] [15] [16] [17], commenting on discussions where other IP socks had previously commented [18], and his condescending, brittle attitude towards other users [19] [20], and similar rationales in RfC votes (compared to earlier socks) [21] [22] [23]. The IP socks merger/deletion rationales are often very similar to the arguments his IP socks made back in late 2020, during the mass merger debacle on the Weather Projects in late 2020, which was one of the main reasons the project implemented a 3-month merger moratorium. Some of the IP talk page activity also resembles that of PlanetsForLife, one of his most recent sock accounts, as seen here [24] [25]. Almost every one of the listed IPs were recently active, especially the last 2, so I strongly recommend blocking each of them. The IPs with more extensive editing activity should receive a longer block. While the last 3 IPs geolocate to Washington State, instead of New York State (Andrew5's known state of residence), I believe that this is due to him utilizing either a VPN or Proxy service, or being on vacation. The behavior from each of these IPs are similar enough to each other and other recently-blocked socks that they're all probably this LTA. I'm also requesting a sleeper check on the IPs, in case he has made new sock accounts for more Extended Confirmed gaming (which he has done before). LightandDark2000 🌀 ( talk) 20:23, 23 February 2022 (UTC) reply

Please do not mass-revert his content additions, as they're actually usually accurate. Even if some of them are unsourced. If his content additions are reverted, they'll have to be readded to those articles again. LightandDark2000 🌀 ( talk) 20:23, 23 February 2022 (UTC) reply
Added some more, based on the admission. Please run a check on the user account and the IPs. The user account also needs to be indeffed. LightandDark2000 🌀 ( talk) 21:45, 23 February 2022 (UTC) reply

Comments by other users

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

(on a different IP) Ok, I’ll admit it. I am block evasion on Wikipedia. But please please hear me out. First of all, Humiebees is not me and we have totally different interests, and the Phoyner accounts was indeed my friend. Also, PFL isn’t me. But those IPs are. I figured if I wasn’t going to get unblocked, that I should still help out Wikipedia. I wanted to improve Wikipedia even though I knew I couldn’t. So I made massive edits to Wikipedia articles to try to improve the site, make it more comprehensible to readers and to just make Wikipedia Storm articles better in coverage. I want to thank LightandDark2000 for crediting me to my public contributions, and for asking them to not mass revert my contributions. I am not using a VPN, I used multiple public IPs in New York, and then took a trip to Washington. I have used other IPs as well I will disclose shortly, but I did all of this to try to improve Wikipedia. These storm damage estimates I am adding in at a serial rate allows people to know the true cost of these storms, and that’s just one of the things I did. I really regret all the sins I have done to Wikipedia, because I really just messed up everything. @ Bbb23:, I am truly sorry for sending you that threatening email, I was simply in the moment and couldn’t think straight. I could’ve had such a nice future on Wikipedia, and I threw it away. I know I will not be unblocked, but can I at least have a standard offer attempt where I can then be unblocked? I really mean what I said that I can become a productive Wikipedian, because I think I have demonstrated that. 65.144.40.106 ( talk) 21:15, 23 February 2022 (UTC) reply
As I compile a list of other IPs I’ve used (104.246.113.199, 160.72.80.50 are the two I found so far), I want to make a note that many of them are public, the Washington IPs I will be leaving the state tomorrow, and the 4th IP from bottom belongs to JFK Airport, so please keep that in mind when blocking. 65.144.40.106 ( talk) 21:22, 23 February 2022 (UTC) reply
There were a few Wikipedia accounts I used in the last little bit, but the only one I remember using was 4WeatherNerd. I’ll look through some histories and find others. 65.144.40.106 ( talk) 21:30, 23 February 2022 (UTC) reply
Although stale, I do remember using TornadoFan45 and 50.74.160.74. Back then I was using the unreliable DailyRecord, recently to be more reliable I switched to NOAA’s official Database. 65.144.40.106 ( talk) 21:37, 23 February 2022 (UTC) reply
Your only chance at a Standard Offer is to go 6+ full months without any socking or editing anywhere. Actually, with your level of socking, you'd probably need a minimum of 12 months without socking before Stewards would be willing to Unlock your main account. And you'd also have to explain your abusive behavior, including various personal attacks and Anti-Semitic comments that came to our attention over the last year. An apology would be necessary at a minimum, but with this extent of abuse, it would be extremely difficult for you to be allowed back, if ever. You've burned down nearly all of your bridges at this point, and if you continue, it's very likely you'll never be welcomed back. LightandDark2000 🌀 ( talk) 21:45, 23 February 2022 (UTC) reply
When have I ever made anti-Semitic comments? I am a Jew myself. I believe the comment I made, was that Ghana wasn’t notable, and I’m sorry for this because I know I insulted a lot of people not just from Ghana, but from Africa. Also, personal attacks have been one area I have been trying to avoid. I just feel terrible making them, so I’m sorry for any I have made because I never intend them as such. Also, I find it too hard to stay off Wikipedia. From February to October, I didn’t make any edits because I am not PlanetsForLife, it was just someone who had the same interests as me in the same area, and the IP must’ve started to edit a day after I was blocked (a tragic coincidence). I just need to become more mature. I swear it’s just too hard to hold down these temptations. That’s why I made the accounts, I literally couldn’t hold back my temptation to edit but couldn’t wait until I could go back to a public IP address, as I didn’t want to out 67.185.37.186 was still my IP (maybe I mistyped it, it’s very prolific). I know this is not going to get me unblocked, I just wanted to get my story out there when I had the chance. 65.144.40.106 ( talk) 21:52, 23 February 2022 (UTC) reply
I also understand it will take 6+ months and in my case could take a year (hence why when I applied after only 6 months, it was declined, both at WP:UTRS and ArbCom), but I was wondering if something like 8–10 would be sufficient. I swear, it’s just that the longer I have to wait, the more likely it is that I slip up, and the reason I began socking in the first place was, and it was the worst thing I could’ve done and i’m sorry for it, was because I realized what’s the point of waiting 6 months, having it denied, then finding another account, I just figured IP block evasion is easier if no one knew. And no one found out for over 3 months, and had I not returned to my old ways, no one would have found out. So L&D, I’m sorry that I did that because not only did I probably hurt your feelings, but it also caused everyone to find out. I shouldn’t have gotten so cocky when I went to Washington but then again, I just shouldn’t have block evaded. I know I shouldn’t even be editing, but I just thought it would be better for me if I apologized now. Also because this is a public IP, I will never be editing from here, and t after tomorrow I will not have access to the 12 IP, the 209 IP and the 198 IP and the other from Washington. So please don’t block those for more then 31 hours. 65.144.40.106 ( talk) 22:03, 23 February 2022 (UTC) reply

My initial reason I did the socking was because I didn’t know socking was banned until February 2020. When I created Andrew5 and Guttmana9 I thought it was ok to do one on phone and one on computer but I was wrong. (My first edits to Wikipedia were on 47.16.99.72 in April 2018, this was a year after that but that IP was since relocated and hasn’t been used since the global block expired in November 2020.) and because I got no block notice, I didn’t know how to appeal it, hence me using UTRS. I still didn’t know with ImtheOneKhaled and didn’t get to the SPI in time, so even in September I didn’t know. Now, I know I have to justify my socking since then, I just thought I could try to make the encyclopedia better. From interstate articles, shifting over to weather during September (I got interested mainly because of Hurricane Laura), and because my IP shifted due to Hurricane Isaias knocking out the power, I had a chance. I wanted to do everything my I could to not get caught, but I clearly failed at it. And all these socks that aren’t even mine just mean I have to wait even longer to get unblocked. PFL likely ruined my standard offer attempt that I made. When i used 69.116.96.17, and all the edits got reverted I thought they found out, but I should’ve stopped when the initial block of 98.116.15.128 (or whatever) was placed. But I chose not to, and now I have to live with the consequences. Because the other school IP was blocked, this means no one at school could edit Wikipedia. Also, some other accounts and IPs I remember using now were 24.189.217.187, Blizzard45678, 67.82.182.94 and 70.23.39.2. I am listing IPs that are stale because I will need to do so anyway when I take on the standard offer, so I am doing it know to get the admission out of the way. 209.201.121.4 ( talk) 13:27, 24 February 2022 (UTC) reply

I will never be editing from this IP again due to me leaving Seattle. Good bye. 209.201.121.4 ( talk) 13:53, 24 February 2022 (UTC) reply

Also please don’t block this IP, it belongs to the airport at Seattle and I will be leaving it for a flight extremely shortly. That being said, I did use 209.53.224.34 while I was in Vancouver, but as I am going to the east coast please don’t block it as it belongs to an aquarium. 198.134.98.50 ( talk) 16:19, 24 February 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

12 August 2022

Suspected sockpuppets

I am not an expert in storm socks, but the above users appear to be all the same as each other, and I've seen some intersection with socks of Andrew5, so I figured this was the best place to file this. Similarities: (1) usernames, (2) recent accounts, (3) no special tags for editors or platforms, and (4) they don't act like new accounts, i.e., knowing templates and hats I'd never even heard of (broader instead of main). Bbb23 ( talk) 20:30, 12 August 2022 (UTC) reply

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

24 October 2022

Suspected sockpuppets

Started editing today and one of their first edits was on Talk:Tornado outbreak of December 10–11, 2021 to propose a split, which was previously proposed by a blocked sock (47.16.96.33) last month, with the exact same reasoning. They also have only edited weather-related articles, which the previous sock did as well. Confusing chain of sock references that go through like 4 different accounts, so I put Andrew5 as well, but I am unsure if that is the main/first sock account of this editor. Direct correlation to 47.16, which was confirmed as a sock. Elijahandskip ( talk) 17:15, 24 October 2022 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
Just knowing about a discussion doesn’t mean I’m a sock. However I was admit I was informed of this by off wiki means. 173.68.1.128 ( talk) 17:44, 24 October 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

01 November 2022

Suspected sockpuppets

69.118.235.133 & 71.183.166.47 both edited a split proposal on Talk:Tornado outbreak of December 10–11, 2021 as their 20th edit and 1st edit on Wikipedia, respectively. The split proposal has been proposed twice by the same sock master (Under User:47.16.96.33 and User:173.68.1.128) and all four accounts (two blocked and two new suspected) have an interest in weather.

170.24.150.2 gave weird vibes to myself and United States Man (Extra off-SPI discussion here) as they started editing weather-articles 4 days ago (October 27th) and suspiciously, the last blocked account of the sockmaster was 173.68.1.128, which was blocked the day after this account started editing (but three days before the blocked account (173.68.1.128) messaged in the SPI after being suspected/accused of it.) Suspecting all three are potentially the same editor as none of them have edited on the same day and all have an interest in weather articles and they all never edited the same day as the previous blocked sock (173.68.1.128). Elijahandskip ( talk) 03:58, 1 November 2022 (UTC) reply

Comments by other users

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

There have been quite a few cases of an apparent IP-hopping editor on tornado-related articles and their talk pages. It has been going on for a while. One aspect of these IPs that first jumps out is their behavior indicates knowledge of the workings of Wikipedia beyond what would be expected of a new editor. Other traits, that have led me to, at times, suspect these IPs are Andrew5 are often confrontational attitudes, and frequent allusions to Wikipedia policy and guideline pages. 47.21.202.18 ( talk · contribs · WHOIS) seems to have been the most frequent ones that come up. I know this is old evidence, but in once such instance 47.21.202.18 added a section to Tornado outbreak of March 5–7, 2022. After that was reverted 69.116.96.17 ( talk · contribs · WHOIS) then readded the section with accusations of WP:STATUSQUOSTONEWALLING and brought the matter to ArbCom. While this would normally be considered stale, I'll note that both IPs have continued to edit many of the same weather-related articles. This is mainly to establish the continuing trend of IP-hopping. More IPs may need to be added in the near future. Honestly, this sort of pattern of an IP-hopping editor, up to and including recent comments at Talk:Tornado outbreak of December 10–11, 2021. This user has basically admitted to IP-hopping in the past, as at Wikipedia:Sockpuppet investigations/Andrew5/Archive#23 February 2022. TornadoLGS ( talk) 04:51, 1 November 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

I'm confident all the IPs mentioned are Andrew5. Due to differing stability:

Closing. DatGuy Talk Contribs 07:28, 1 November 2022 (UTC) reply

02 November 2022

Suspected sockpuppets

170.24.150.113 has confirmed via Wikipedia:Articles for deletion/2012 Henryville tornado that it is a school IP address on Long Island, while WHOIS confirms the other IPs are all from the same place on Long Island or Virginia (locations of previously blocked IPs). Each new IP address tries to act like a different person, trying to make it seem like a coincidence that multiple anon users all pop up in the same place at once with the same agenda, same general in-depth knowledge of Wikipedia, and same general attitude. Several other IP addresses were just blocked a couple days ago for the same odd behavior at the same weather articles. Elijahandskip and TornadoLGS have both had encounters with this situation and may care to comment here.

The previously blocked IPs are 170.24.150.2 ( talk · contribs · WHOIS), 71.183.166.47 ( talk · contribs · WHOIS), 69.118.235.133 ( talk · contribs · WHOIS), 47.21.202.18 ( talk · contribs · WHOIS), and 69.116.96.17 ( talk · contribs · WHOIS). It is suspected that all of these accounts are the same person, despite trying to act like different people, given very similar behavior in the same place at the same time. United States Man ( talk) 23:06, 2 November 2022 (UTC) reply

Comments by other users

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

I'll note that most of the listed IPs have shown an interest in the newly created article 2012 Henryville tornado and, despite claims to the contrary, it seems unlikely that a bunch of people would suddenly start editing Wikipedia for the first time upon hearing about a newly created article about an event that happened ten years ago. TornadoLGS ( talk) 01:03, 3 November 2022 (UTC) reply

Really? This is a public IP,hence the collusion makes sense. Some of these IPs really have no evidence. The 148 IP, really? Attribution is in the TOU, and AFC is the only way for IPs to create articles. 71 seems to be no evidence. And making every IP working to save Henryville to get it deleted is a witchunt. -- 170.24.150.113 ( talk) 11:19, 3 November 2022 (UTC) reply
I'll elaborate, since classes cut me short. What I mean is, even if it's unlikely that all the new accounts would gravitate towards the article, WP:AGF prevents us from assuming that it is the cause without more concrete evidence. -- 170.24.150.113 ( talk) 12:03, 3 November 2022 (UTC) reply
The same general knowledge of the same events and the same knowledge of WP policies and guidelines despite not being an autoconfirmed user point to the fact that all of these are the same person. Not to mention the fact that previously blocked socks have come from the same addresses. The only defense from the accused points just sounds like grasping at straws. United States Man ( talk) 18:32, 3 November 2022 (UTC) reply
Adding to USMs comment, this all fits the pattern of previously known socks. WP:DUCK applies. TornadoLGS ( talk) 20:55, 3 November 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

30 November 2022

Suspected sockpuppets

170.24.150.113 is a confirmed sock of Andrew5 that is continuing to be allowed to edit freely on Wikipedia, thus making a complete mockery of this entire process. @ TornadoLGS and Elijahandskip: can testify to this as well. United States Man ( talk) 19:06, 30 November 2022 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
How dare you make this accusation. Aggressive Wikipedia users are quite common, you are one yourself.-- 170.24.150.113 ( talk) 19:06, 30 November 2022 (UTC) reply
It's not an accusation. An admin confirmed it in a previous report lol. United States Man ( talk) 19:07, 30 November 2022 (UTC) reply
No they didn't. Quit being a brat.-- 170.24.150.113 ( talk) 19:08, 30 November 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

4 December 2022

Suspected sockpuppets

Previously blocked socks of Andrew5 that are continuing to be allowed to edit freely on Wikipedia, thus skirting around the sockpuppet process. I suspect there are more IPs around in which the user edits the same types of articles and displays the same editing characteristics and abrasive behavior toward others. WP:DUCK applies in those cases. United States Man ( talk) 20:45, 4 December 2022 (UTC) reply

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

13 December 2022

Suspected sockpuppets

Three different IPs making the same edit with the same argument at Hurricane Isaias. The different IPs are an attempt to skirt the 3RR or to sway talk page discussions and has been done multiple times with previously blocked socks. These IPs routinely edit the same types of articles and generally perform the same types of edits. The fourth and fifth make similar edits as well. WP:DUCK applies here. The WHOIS addresses all point to the same town (and many cases, same address) on Long Island, or towns immediately adjacent. Most previously blocked IP socks of Andrew5 have this address (or town) in common. United States Man ( talk) 06:32, 13 December 2022 (UTC) reply

Comments by other users

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

Given our issues of playing whack-a-mole with IPs, I suggest page protection on this case. TornadoLGS ( talk) 20:04, 13 December 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

15 December 2022

Suspected sockpuppets

This group of IPs is continuing in the same pattern as previously observed by Andrew5 socks. This includes editing (including edit warring) across multiple IPs, a confrontational attitude when edits are reverted or criticized, and a focus on storm-related articles. The most recent activity has involved edit warring at 2010 New Year's Eve tornado outbreak ( [26]], [27], [28]) and Hurricane Isaias tornado outbreak ( [29], [30], [31]). See also those page histories and IP talk pages. Other IPs were mentioned at the previous opening of this case. It seems saying "How dare you" has become a calling card of theirs. In an earlier report here, the closing admin RoySmith opted for page protection since this person seems to change IPs faster than they can be blocked, but stated: If that proves ineffective, we can look at stronger measures. I'm not sure what that would involve. This person has been on quite a few weather articles. TornadoLGS ( talk) 22:14, 15 December 2022 (UTC) reply

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

17 January 2023

Suspected sockpuppets

[32] [33] [34] 3 complete almost duplicate comments on a weather-related article. When asked to start a discussion about it, instantly went and started a noticeboard, which has been the behavior of this sockmaster who likes to escalate issues. 69 started editing weather articles on January 6 then stopped until January 10, then stopped until January 17. None of the three accounts edited at the same time. Based on the behavior, talking about “core policies” and such (similar to the Aon/NOAA debate which had multiple sock accounts from this sockmaster & bring it straight to ArbCom)… WP:DUCK applies here. Elijahandskip ( talk) 21:54, 17 January 2023 (UTC) reply

Comments by other users

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

Adding to this report 69.127.228.206 ( talk · contribs · WHOIS) and 47.19.209.232 ( talk · contribs · WHOIS) have both engaged in a small revert war at Tornado outbreak of December 10–11, 2021, showing the same confrontational attitude and pattern of IP-hopping as is typical. Both of these IPs appear similar to ones previously used by Andrew5. Filing a report at an Andministrative noticeboard is also consistent with past behavior. Previous closing admins have mentioned page protection as a remedy. TornadoLGS ( talk) 22:53, 17 January 2023 (UTC) reply

Page protection is not a remedy because said IP addresses continue to edit other articles. The best remedy would be to block the IPs so a sockpuppet isn’t allowed to freely edit Wikipedia and flaunt the whole sockpuppet idea and process. United States Man ( talk) 13:58, 18 January 2023 (UTC) reply
This, to me, seems like an attempt for WP:WEATHER to gain an edge in a dispute. Firstly, let me say there was a flaw in the filing - the ArbCom filing seemed to have not been over NOAA/Aon drama, but rather over whether or not a section could be added to Tornado outbreak of March 5-7, 2022. Elijahandskip is trying to own the template for the deadliest events in 2023 and is inserting WP:OR into the article. Important point to note - I didn’t even bring it up to the notice board for even me! I brought it up to the noticeboard because someone else noticed it! Are we now going to file an SPI on them because of that? i thought not. So this seems to be a bias against IP editors. Truly shameful. TornadoLGS, Elijahandskip, USM, ChessEric and Poodle23, amongst many others, have been treating IP users as less to regular users, and frequently look for a way out. As can be seen in the previous SPI, only 2 IPs since November 2 have been blocked. One were previously blocked, and the other deserved a block for egregious WP:NPA violations. That entire range is now blocked. The evidence seems to be grasping at straws as a way to “win” the debate, and this behavior from the WikiProject is unacceptable and is why they are in so much trouble to begin with. Additionally, as this IP belongs to a synagogue, this appears to be antisemitism as well. 69.127.228.206 ( talk) 20:25, 18 January 2023 (UTC) reply
Now that last comment seems to be so much speculation and extremely judgemental, especially since every user you just mentioned is a 100% separate user & deals with multiple users who edit under an IP. But are you saying the other two IP’s listed in this are not you? If so, then why was the comments almost duplicate (including the 2nd comment even saying “still”, indicating it was the same person as before? Also, I think your “I didn’t even bring it up to the notice board for even me! I brought it up to the noticeboard because someone else noticed it!” is a direct admission of multiple users on the same account. The way I read that, you said a user was on that IP at 21:17 on January 17 on a talk page and a 100% different user was on the account at 21:30 on January 17 who created the IP & who just happened to continue the exact same discussion? To answer your other question, I wouldn’t have even thought about starting an SPI until I saw three unique IP accounts, following the same pattern that has been seen on multiple weather-related articles since July 2022. Admins have even confirmed multiple users (most pre-November 2022) as being the exact same person. If you are not connected to any of the other users, then you wouldn’t be blocked. That simple. But the editing pattern almost speaks for itself, unless it is an exceptional coincidence. Elijahandskip ( talk) 20:40, 18 January 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Blocked IP 69.127.228.206 for two weeks. The other IPs haven't edited recently enough to bother. There is a tremendous amount of IP hopping in this case and it's unfortunately hard to do much about it. Closing. Bbb23 ( talk) 20:44, 18 January 2023 (UTC) reply

6 February 2023

Suspected sockpuppets

I may be jumping the gun, but this revert edit is similar to what I've seen in the past with AON/NOAA disputes, especially since different IPs doing the reverts seem to be the norm. Please look into this. Thanks. ChessEric ( talk · contribs) 22:07, 6 February 2023 (UTC) reply

I thought I'd thrown in a second IP as well. The IP was in the last investigation, but was not blocked due to a lack of recent edits. However, editing on this account returned the day after the investigation was closed and it had an aggressive tone that I've seen in the past. I looked back through the edit history and found some similar patterns to past socks (i.e., [35], [36], and [37]). Please look into these. Thanks. ChessEric ( talk · contribs) 22:52, 6 February 2023 (UTC) reply

Comments by other users

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

The WHOIS location and edit history of this account match similar blocked accounts as well. United States Man ( talk) 22:20, 6 February 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

23 February 2023

Suspected sockpuppets

1st IP appears to have been caught by United States Man, so I bought it here. This edit ( [38]) appears to have been a follow-up to this one ( [39]) as well and Andrew5 has been known to use multiple IP addresses for edit warring. The 2nd IP has been in the last two investigations and appears to start editing only after the investigations conclude. Please look into these. Thanks. ChessEric ( talk · contribs) 18:50, 23 February 2023 (UTC) reply

I just added a third IP whose WHOIS matches Andrew5. They apparently didn't like this revert I did, so they reverted me and left me this warning on my talk page. I will admit it gave me a good chuckle this morning, especially since the revert I did said nothing about the IP being a sock. Anyway, please look into these. Thank you. ChessEric ( talk · contribs) 16:40, 24 February 2023 (UTC) reply
I just nabbed a 4th IP that has the same WHOIS as the 2nd one. I'm having a little too much fun confronting him though; I'll try to tone it down so I don't break any rules. ChessEric ( talk · contribs) 22:34, 25 February 2023 (UTC) reply
Found a 5th IP who commented in this discussion. The WHOIS matches the 2nd and 4th IPs. ChessEric ( talk · contribs) 15:26, 26 February 2023 (UTC) reply
6th IP's WHOIS matched 2nd, 4th, and 5th. ChessEric ( talk · contribs) 15:28, 26 February 2023 (UTC) reply
8th, 10th, 11th, and 12th IP's WHOIS match other ones on this list. The 8th and 9th ones don't, but their both located at the same place in Colorado, so something is going on with those 2. ChessEric ( talk · contribs) 15:41, 26 February 2023 (UTC) reply
Actually, I'm a bit confused now. The Ashburn location is a Verizon building ,so why are there so many accounts out of there? Is it like a centralized tower or something? ChessEric ( talk · contribs) 20:04, 26 February 2023 (UTC) reply
Just added a new one with a matching WHOIS. ChessEric ( talk · contribs) 23:03, 1 March 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • Uh…I don’t even know what to say. Is there something going on, because I don’t know what any of this is. 98.116.45.220 ( talk) 19:45, 26 February 2023 (UTC) reply
  • WHOIS evidence isn’t enough in an SPI case. In this case, right at the top of WP:SPI, it says Evidence is required. When you open the investigation, you must immediately provide evidence that the suspected sock puppets are connected. The evidence will need to include diffs of edits that suggest the accounts are connected. (This requirement is waived if the edits in question are deleted; in this case just provide the names of the pages that the accounts have been editing.) You must provide this evidence in a clear way. Vaguely worded submissions will not be investigated. You need to actually show why your suspicion that the accounts are connected is reasonable. Concision is key. Evidence should be presented in a concise format. Because of the length of the backlog, cases with clear and concise explanations and evidence are handled the most quickly. ChessEric has provided very few diffs and just gave WHOIS evidence. However, (1) WHOIS isn’t always right, (2) this is a very densely populated area (Long Island) and comes from different organizations, and (3) we seem to only be served by a few towers. Also, ChessEric seems to be opening a WP:WITCHHUNT for paranoia reasons to get IPs out of WP:WEATHER. That isn’t allowed. 71.125.62.146 ( talk) 21:25, 3 March 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

2 March 2023

Suspected sockpuppets

I know the previous case just closed, but I found another IP whose WHOIS popped up as a common Andrew5 location. He seems to be keen on putting records ( [40]) into articles and that's what tipped me off here. Additionally, this IP has previously said that they wanted me topic-banned from the weather project based on the canvassing issue that occurred on February 9, although my ban was for threats of violence, which I do regret. Regardless, the IP appears to be a repeat offender of Andrew5. Please look into this. Thanks. ChessEric ( talk · contribs) 23:10, 3 March 2023 (UTC) reply

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

8 April 2023

Suspected sockpuppets

IP addresses of Andrew5 have been repeatedly trying to make the WP:Weather a contentious topic, which leads up to this edit not too long ago. It was completely off-topic and unnecessary. I've been keeping my mouth shut about these, but I'm tired of seeing this so I want one of IPs nipped in the bud. Thank you. Chess Eric 22:21, 8 April 2023 (UTC) reply

Comments by other users

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

Added two more from Talk:1932 Deep South tornado outbreak, where both IP addresses employee the same behavior and edit history (along with WHOIS location) as many other instances of Andrew5. United States Man ( talk) 19:37, 9 April 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

27 May 2023

Suspected sockpuppets

98.113.8.17, 69.118.237.29, and 47.19.209.230 matches the most recent editing pattern for 98.116.45.220, a recently suspected sock: Weather and baseball (looking at most recent 50 edits for all accounts show that). They all match the most recent blocked sock as well 71.125.32.0/19 with weather and baseball. While 47.19.209.230 and 69.118.237.29 have not edited recently, they all commented in a discussion. Confirmation of if they are or are not a sock is requested to know of the discussion was sock stacked or not since 3 of the 5 editors involved seemed to match the sock’s editing pattern. Possibly WP:DUCK. Elijahandskip ( talk) 16:11, 27 May 2023 (UTC) reply

  • I just added 75.99.68.66 to the list as well. Edited recently dead match with the others with baseball and weather interests in the last 20 edits. Very clear WP:DUCK from the ip-hopping sock master. Elijahandskip ( talk) 00:17, 28 May 2023 (UTC) reply
    I just added a fifth one, 216.165.125.249, as well. Dead match with multiple weather and baseball related edits on July 12 (see contributions). Noting, the commented in an ongoing merge discussion that affects 3 articles, so if they are a sock, a block or at least confirmation is needed. The Weather Event Writer ( Talk Page) 00:20, 13 July 2023 (UTC) reply

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

30 July 2023

Suspected sockpuppets

71.125: WP:DUCK match in contribution history of weather-related edits and baseball edits (see contribution history for July 16 & 30, 2023). 98.166 was found after looking through the 2023 Chicago Cubs season article, which both accounts edited. July 23 and July 16 (right before the 71.125) contribution histories are WP:DUCK matches as well. Noting that 71.125.36.50 Was previously blocked on WHOIS evidence and then appealed saying, “Way too many of these Nassau County IPs have been blocked over the past 3 years. We just want some stability”, which is basically a SOCK confirmation. Can the IPs be perm blocked given multiple day usages and usages after the previous block as well? The Weather Event Writer ( Talk Page) 15:31, 30 July 2023 (UTC) The Weather Event Writer ( Talk Page) 15:31, 30 July 2023 (UTC) reply

Noting I have added 104.246.113.199 & 72.68.134.254. 104.246.113.199 Edited again on July 19, 2023 (after IP sock block — See their contribution history). 72.68.134.254 was discovered through WP:DUCK editing on Draft:January 2023 North American storm complex, which numerous IPs linked to this sockmaster have edited. Maybe an SPI investigation into all the IPs that have edited the draft should be looked at. No solid reason newer IPs (i.e. 72.68.134.254) should be edited a draft, which is basically only IP edits in the last 6 months. Strong WP:DUCK connection. The Weather Event Writer ( Talk Page) 23:15, 31 July 2023 (UTC) reply
69.119.89.11 was added as a WP:DUCK match (Weather and baseball edits) on the same days on July 15 and 22. The Weather Event Writer ( Talk Page) 23:34, 31 July 2023 (UTC) reply

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

11 August 2023

Suspected sockpuppets

See contribution history with a WP:DUCK match of weather and baseball edits on the same day. Also, they were previously blocked on this IP address (February 2023) and continued editing on it, so this may deserve a perm block for the IP. The Weather Event Writer ( Talk Page) 22:57, 11 August 2023 (UTC) reply

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

11 August 2023

Suspected sockpuppets

WP:DUCK, matching baseball and weather edits on the same day, seems like Andrew5. Baseball edit here, the weather edits are on this page's history. Tails Wx 02:46, 12 September 2023 (UTC) reply

Also throwing in 75.99.8.58 for match of weather and baseball edits as well. Tails Wx 00:48, 24 September 2023 (UTC) reply

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

12 October 2023

Suspected sockpuppets

WP:DUCK confirmation on October 12, 2023 (Baseball and weather (winter storm article) edits within 4 minutes. This sock account was used previously on June 14, 2023. Can we seriously just start perm blocking the IPs? This has been going on way too long, taking up the time of editors and administrators practically every month. The Weather Event Writer ( Talk Page) 18:57, 12 October 2023 (UTC) reply

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'm not willing to block indefinitely, but I'll be likely to consider longer blocks moving forward. I sampled some of the IP socks in the archive and am not seeing any evidence that lengthy blocks will cause much collateral damage. This ducky IP is blocked for a year. Closing. Firefangledfeathers ( talk / contribs) 03:59, 14 October 2023 (UTC) reply

29 October 2023

Suspected sockpuppets

Otis2023 made 3 edits (their only 3 edits on Wikipedia) on October 27 to Draft:Hurricane Calvin (2023) and Draft:Tropical Storm Sonca (2022). ThatBigSwiftie1989 made 2 edits (their first two edits) to the same draft articles. Edits on Hurricane Calvin’s draft are identical [41] [42]. Either SOCK inventions or accounts needing to be linked together in some fashion. Given the identical comments in an AfC, there may be some SOCK master before Otis2023, since they have knowledge of at least 2 draft articles as well as how to make AfC comments. Thought, this may be User:Andrew5 alts (unsure), since Andrew5 (sock master) likes to edit winter weather articles and ThatBigSwiftie1989 made their 3rd/4th edit on two winter articles within minutes of starting to edit. The last Andrew5 confirmed alt, User:108.54.87.90 edited winter storm articles as well, so a location-check is probably needed to verify if it is Andrew5. The Weather Event Writer ( Talk Page) 21:22, 29 October 2023 (UTC) reply

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

Dreamy Jazz talk to me | my contributions 22:50, 29 October 2023 (UTC) reply

04 November 2023

Suspected sockpuppets

Their only edits today was to nominate Hurricane Calvin (2023) for deletion with the exact same reasoning as their other SOCK accounts gave to prevent it being accepted at AfC (which it was). WP:DUCK/suspected sock confirmation edits: Sock 1, Sock 2, Suspected Sock. The Weather Event Writer ( Talk Page) 15:33, 4 November 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
And too bad you can’t use CheckUser to find out. Maybe Lidia2024 and Andrew5 are the same user also. 69.118.232.58 ( talk) 19:50, 4 November 2023 (UTC) reply
  • @ WeatherWriter: I just checked the block logs of the IP's, and all of them you listed were previously blocked as sockpuppets as early as January, with the third one's previous block actually mentioning Andrew5. I also wanted to mention the DamageReportAdder account, who added damage totals with non-NOAA sources such as Aon to Tornadoes of 2023 and other pages, which I noticed that he has a history of doing with previous IPs/accounts. ChrisWx 🌀 ( talk - contribs) 02:07, 5 November 2023 (UTC) reply
    Lol the evidence for accusations seems to be really really really really really low. Aon? Really? Are you about to call Destroyeraa an Andrew5 sock because they used Aon? Or HikingHurricane? Besides, the original accounts behind the Aon debate geolocated to South Carolina, Texas and Arizona, whereas Andrew5’s known state of residence is New York, with his only known vacation being made to Virginia and the Pacific Northwest. The bar is really low for evidence for IPs, yet when the exact same evidence is filed against an experienced editor, all of a sudden it is discarded. This seems like a violation of WP:5P4.-- 69.118.232.58 ( talk) 14:23, 5 November 2023 (UTC) reply
    Also noting that the DamageReportAdder account's only purpose seems to be to add Aon to weather-related pages, here's an example of previously blocked Andrew5 sock doing so, then reverting back to it with an argumentative tone. It's entirely possible that the DRA account is someone who wasn't aware of the NOAA damage precedent trying to add the totals in, but I'm mentioning it because it seems suspicious. As for Destroyeraa and HikingHurricane, they have a very different editing style, the edits were before its reliability was established, and simply citing an edit or two of theirs does not prove that they are socks. ChrisWx 🌀 ( talk - contribs) 16:04, 5 November 2023 (UTC) reply
    Citing one or two edits worked for many Andrew5 IPs in the past, check the archive. 69.118.232.58 ( talk) 21:32, 9 November 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

21 November 2023

Suspected sockpuppets

User copied content from the talk page of a recently blocked IP address ( [43]) and edited weather/sports edits on the same day as that copied content (which was weather-related): sports/ weather 1 & weather 2. WP:DUCK reasoning seems strong and the blocked IP which had content from their talk page copied by this user admitted in a ban appeal less than 48 hours ago to editing on multiple IP addresses. Checkuser is requested strictly on WP:DUCK evidence. The Weather Event Writer ( Talk Page) 23:55, 21 November 2023 (UTC) reply

Also noting this user was previously blocked in 2022 for a year for block evasion, which also supports a WP:DUCK check, given the connection to a recently blocked account. The Weather Event Writer ( Talk Page) 05:23, 22 November 2023 (UTC) reply

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

26 November 2023

Suspected sockpuppets

Typical WP:DUCK evidence in their edit history (Weather/baseball). They also basically confirmed they are a sock by reverting admin @ K6ka: on Talk:San Francisco–Oakland Bay Bridge, who reverted a now blocked SOCK (71.125.62.208), who was causing disruption and edit warring on the page. I'm assuming Andrew5 is the master given the weather/baseball history, but K6ka knowns the sock master as they blocked this sock earlier today. The Weather Event Writer ( Talk Page) 00:06, 26 November 2023 (UTC) reply

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

26 November 2023

Suspected sockpuppets

Check edit history. IP re-engaged in the exact same four edit warring discussions as the previous IP, including reverting the blocking admin who did a SOCK-disruption revert on Talk:San Francisco–Oakland Bay Bridge. Also a fun SOCK confirmation saying “stop bribing admins to block innocent IPs. This is a violation of WP:PAID”. The Weather Event Writer ( Talk Page) 17:22, 26 November 2023 (UTC) reply

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

06 December 2023

Suspected sockpuppets

After not editing for a month, their third edit was to re-revert something previous Andrew5 SOCKS were reverting. The previous user to revert this was 47.21.202.18, who was blocked for 2-years as Andrew5. Also, the user who reverted it prior to 47.21.202.18 was 47.23.6.178, who was also blocked as Andrew5. Unlike other times, this is all I have (not solid WP:DUCK evidence), which is why checkuser is requested to see if this is Andrew5, or a separate editor. The Weather Event Writer ( Talk Page) 15:53, 6 December 2023 (UTC) reply

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

WeatherWriter, CheckUsers will not, for privacy and policy reasons, publicly divulge a connection between a registered user and an IP. IP socking reports are made or broken on behavioral evidence. A clerk will likely be by soon to decline the CU request. I'm inclined not to block based off of the edits so far. I'll keep an eye on them; you should too. Firefangledfeathers ( talk / contribs) 16:07, 6 December 2023 (UTC) reply

11 December 2023

Suspected sockpuppets

First edit ever was to re-create Draft:Late October 2012 North American blizzard, which was deleted earlier today for being created by a Andrew5 sock. The Weather Event Writer ( Talk Page) 19:41, 11 December 2023 (UTC) reply

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

12 December 2023

Suspected sockpuppets

Most of these IPs have already been previously blocked as Andrew5 socks in the past, but they have edited since their block has expired with similar behavior to their socks, such as their interest with the Northeast United States, including Long Island, in their weather-related edits, editing their usual targets, such as Tornado outbreak of December 10-11, 2021 (removing size tag, previous socks have gotten into similar conflicts on page), and addition of snow/rainfall records on pages, which is common sock behavior for Andrew5. Some IPs haven't edited in multiple days, but since they usually edit on static IPs, they will still need to be blocked for a long period of time. A rangeblock may also be needed since they are likely on similar ranges. If there are any problems with this, please let me know. Thanks, ChrisWx 🌀 ( talk - contribs) 02:08, 12 December 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • I am not sure about the other three, but 69.116.96.17 is Andrew5 per their November 2022-23, 1 year ban-evasion block. Disruptive or not, that account in edit on November 26, 2023 and Andrew5 obviously is still blocked. So 69.116.96.17 for sure needs a new ban-evasion block (2 years like the other SOCK accounts). The Weather Event Writer ( Talk Page) 02:14, 12 December 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

13 December 2023

Suspected sockpuppets

Blocked before as a sock of Andrew5 and immediately went to edit the draft of TS Bret where the socks from yesterday were editing. Noah, AA Talk 14:08, 13 December 2023 (UTC) reply

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

13 December 2023

Suspected sockpuppets

[44] Same behavior as User:47.21.192.218 that Bbb23 blocked earlier today. Noah, AA Talk 22:10, 13 December 2023 (UTC) reply

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

16 December 2023

Suspected sockpuppets

Only contribution is to reinstate edit from a blocked IP sock, similar attempt to justify his reversion to other socks, and dubiously accusing others of assuming bad faith. Also request a global block, user is known to engage in cross-wiki harassment. ChrisWx 🌀 ( talk - contribs) 21:43, 16 December 2023 (UTC) reply

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

17 December 2023

Suspected sockpuppets

Obvious duck: See this attack against me. Was previously blocked as Andrew5 a few days ago, so needs longer block and global block. ChrisWx 🌀 ( talk - contribs) 15:41, 17 December 2023 (UTC) reply

Added another IP which reinstated a blocked sock's edit on Hurricane Isaias ( diff) and has also previously edited MLB-related pages, the usual Andrew5 targets. Also noting that the range 71.125.32.0/19 has been previously blocked for hosting Andrew5 socks. ChrisWx 🌀 ( talk - contribs) 21:58, 17 December 2023 (UTC) reply
Third IP added, cross-wiki harassment, sent harassing message on Wiktionary. ChrisWx 🌀 ( talk - contribs) 00:20, 18 December 2023 (UTC) reply

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

24 December 2023

Suspected sockpuppets

Duplicate edit on Tornado outbreak of December 10–11, 2021 ( [45]) to previous Andrew5 socks ( 69.118.238.21 & 47.23.40.14) The Weather Event Writer ( Talk Page) 18:50, 24 December 2023 (UTC) reply

Added 157.130.20.198 due to this duplicate edit. The Weather Event Writer ( Talk Page) 19:32, 24 December 2023 (UTC) reply
Added 204.150.3.195 due to yet a third edit on that article, duplicating the text in a now edit-war style fashion and somehow asking me to not file yet another SPI (Nice confirmation LOL!). Noting that 157.130.20.198 is blocked for vandalism at this time as well. The Weather Event Writer ( Talk Page) 20:08, 24 December 2023 (UTC) reply

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

27 December 2023

Suspected sockpuppets

Fairly new account with a similar editing pattern to Andrew5’s basic behavior: Wikipedia:Long-term abuse/Andrew5. A quick check can help verify if they are a true new unique account or Andrew5. The Weather Event Writer ( Talk Page) 03:04, 27 December 2023 (UTC) reply

Reply to @ Blablubbs: — These two edits on Hurricane Dorian add small, trivial-style facts to the article. The first edit actually mentions an MLB team being cancelled (Andrew5 often edits sports articles) (similar to this edit by a blocked sock and the 2nd edit was a trivial fact about a National Park being closed. That park being closed (trivial fact) is very similar to this edit & this edit & this edit by three previous blocked Andrew5 accounts. If I did a deep search through the list of Andrew5 IPs, I could probably link others do him. I forget which IP, but one of the Andrew5 IPs went through and used Accuweather a bunch in the past for snow/rain amounts, similar to this edit. It may be two editors, but the editing pattern seems oddly similar to Andrew5. Also the 3 Andrew5 IPs linked in the report on December 24th oddly all edited on December 24th and this account edited Dec 23/25th. We know Andrew5 didn’t take the Holiday off as they impersonated ChessEric twice on Meta-Wikimedia over the last 3 days. I want to assume good faith completely, but a check to verify if it is Andrew5 or a unique editor would be useful as the pattern seems to basically match the LTA to the letter (excluding personal attacks, which haven’t been on EN-Wiki for a while). The Weather Event Writer ( Talk Page) 01:51, 28 December 2023 (UTC) reply

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

28 December 2023

Suspected sockpuppets

Began their edits today reverting several edits by Yamla, who has just started rollbacks after blocking the previous confirmed Andrew5 sock CrossBayFan. They were previously blocked back on December 16, 2023. For sure WP:DUCK Andrew5 IP address. The Weather Event Writer ( Talk Page) 16:00, 28 December 2023 (UTC) reply

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

29 December 2023

Suspected sockpuppets

Every edit they made was to re-revert rollbacks from Andrew5 socks blocked yesterday by Yamla. Note, they are blocked for 1 week after making a death threat. This is a confirmed sock, block for 2+ years. The Weather Event Writer ( Talk Page) 16:35, 29 December 2023 (UTC) reply

Added 24.193.72.181. Re-reverting Andrew5 rollbacks as first edits today. Obvious WP:DUCK socks. The Weather Event Writer ( Talk Page) 16:43, 29 December 2023 (UTC) reply

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

29 December 2023

Suspected sockpuppets

Only edits as of this report is to attempt, once again, to roll-back edits from previous SOCKS. The Weather Event Writer ( Talk Page) 20:08, 29 December 2023 (UTC) reply

72.80.167.6 added as they went right back to edit-warring on the Andrew5 roll-backs. The Weather Event Writer ( Talk Page) 20:59, 29 December 2023 (UTC) reply

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

02 January 2024

Suspected sockpuppets

Editing sports-related articles and restoring sock edits where they were previously reverted. Also used edit summaries containing personal attacks, before engaging in page-move vandalism on an article where they were reverted, and attacking people who have been working against their sockpuppetry. Account is already blocked/g-locked, but I am requesting a CheckUser to see if there are any more sleepers waiting to gain autoconfirmed like this one. ChrisWx 🌀 ( talk - contribs) 19:25, 2 January 2024 (UTC) reply

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

19 January 2024

Suspected sockpuppets

A brand new account that started editing Draft:January 10-13, 2024 North American storm complex on January 19. On January 18, another new account ( JuneFan2939 was globally locked for being this sock master. 2nd edit ever from WinterStormFan was on the draft and first was on the parent winter storm article. SPI needed to check.

SEPARATE REPORT (NO SPI): Heavy WP:DUCK evidence on 152.179.91.86, who also edited the draft and parent winter storm. They stopped editing on January 15 and JuneFan2939 edited on January 16 on the draft. The IP created the draft and the only other 2 editors to it are JuneFan2939 and WinterStormFan. Can a 2nd administrator (Not checkuser) review the IP on DUCK evidence? The Weather Event Writer ( Talk Page) 23:38, 19 January 2024 (UTC) reply

Comments by other users

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

There is a reason I knew about the draft : Talk:2023-24 North American winter. Also, while I am not JuneFan2939, I doubt that he is related to CreamFan12. CreamFan12 was a vandal who harassed multiple users on Meta Wiki, and does not even exist on enwiki. While JuneFan2939 does exist on meta, they made no edits there and instead made constructive contributions to enwiki. This just seems to be the case of two irrelevant users connecting through a shared IP address. WinterStormFan ( talk) 18:40, 20 January 2024 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

03 February 2024

Suspected sockpuppets

Looks like Andrew has become a Swiftie to avoid detection. A public IP in New York that has previously edited weather articles (similar to Andrew5's previous IP socks) started inexplicably editing The Eras Tour and arguing that a section is a content fork. Then SwiftFan2024 comes and makes the same argument that the IP made. Not requesting CU on the IP for obvious reasons. wizzito | say hello! 03:23, 3 February 2024 (UTC) reply

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

17 February 2024

Suspected sockpuppets

Suspicious new IP (208.253.89.50) that started editing winter weather articles today (just like previous Andrew5 accounts). One of their first edits was adding trivial fact about NPS closing stuff, similar to a previous sock edit. They also did a second trivial addition minutes later. That is making me suspect WP:DUCK. Not to mention that second trivial addition was on January 13–16, 2024 North American winter storm, which was (basically) Andrew5's article with JuneFan2939 and WinterStormFan (recently blocked Andrew5 socks) having about 40% authorship of the article. This account seems to match WP:LTA/Andrew5 to a T. Also, they basically "DUCK confirmed" to be a new IP when editing Talk:June 2021 North American storm complex#Merge, by responding to a merge discussion started by another IP (108.58.71.234) a couple of days ago which also coincidentally is a brand-new editor with only a few edits. DUCK senses tell me this is Andrew5. The Weather Event Writer ( Talk Page) 23:44, 17 February 2024 (UTC) reply

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

18 February 2024

Suspected sockpuppets

[46] [47] - First two edits were to rollback deleted SOCK edits actually on this SPI talk page. CU requested since this is an account and not an IP. The Weather Event Writer ( Talk Page) 23:27, 18 February 2024 (UTC) reply

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

Chastick293 is confirmed to June10393 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki) and some logged-out shenanigans (no comment on the IPs previously mentioned). The technical evidence stretches further still. It all looks very likely to be Andrew5. -- zzuuzz (talk) 00:04, 19 February 2024 (UTC) reply

23 February 2024

Suspected sockpuppets

Restored deleted content added by previous IP sock that was blocked. Account only has 1 edit and was created today. WP:DUCK me thinks? -- MarioProtIV ( talk/ contribs) 15:35, 23 February 2024 (UTC) reply


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

29 March 2024

Suspected sockpuppets

(69.123.50.215) There second edit today (1 minute after their first edit today) was to complete a merge, which Andrew5 was confirmed (via blocked-sock 208.253.89.50) to have participated in along with a possible 2nd DUCK account. Their edit summary commented about that talk page discussion, where only 2 actual users commented + 2 Andrew5 comments. 69.123.50.215 is also working on Draft:December 2023 nor'easter, which is a common theme for Andrew5 socks — Being aware of draft-space weather articles. Seems very DUCKY here, given Andrew5 having confirmed knowledge of that merge discussion and then an unregistered user actually merging that discussion after only 4 registered users (2 commenters, the admin closer, and myself) seemingly having knowledge of said merge discussion…Also the 2nd unregistered user was suspected by myself along with the admin to have maybe been Andrew5, who coincidentally opened that merge discussion. I.e. based on DUCK evidence: Andrew5 wanted to merge the article, commented in it, had others agree, and finally today actually merge that article via a new IP address based on a talk page discussion which had 49 views in the last month. The Weather Event Writer ( Talk Page) 17:27, 29 March 2024 (UTC) The Weather Event Writer ( Talk Page) 17:27, 29 March 2024 (UTC) reply

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

30 March 2024

Suspected sockpuppets

Their first edit since 2007 was to reinstate a SOCK reversion edit saying “The sock is right though”. DUCK block needed on Andrew5 sock here. The Weather Event Writer ( Talk Page) 13:47, 30 March 2024 (UTC) reply

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

31 March 2024

Suspected sockpuppets

Their first edit since January 5 was to yet again revert a SOCK reversion edit for that merge discussion. Easy DUCK account of Andrew5. The account also edit warred for it with Fantastic Mr. Fox. The account was also previously blocked for 1 month for ban evasion. Given previous block and edit warring behavior, requesting the 2-year block which previous Andrew5 IPs have received. The Weather Event Writer ( Talk Page) 15:26, 31 March 2024 (UTC) The Weather Event Writer ( Talk Page) 15:26, 31 March 2024 (UTC) reply

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

06 April 2024

Suspected sockpuppets

DUCKY chances seem high that this is Andrew5. Their first edit on Wikipedia was in an AFD, which is currently nominated for a TNT due to SOCK copyright violations. A confirmed SOCK from Lokicat3345 did edit the article, however, several IP users have also edited the article, including one of the large copyright violations. Andrew5 and/or Lokicat3345 are often is aware of non-mainspace things (like AfDs or drafts). My senses also went up as that AFD comment (their first edit) stated “We are becoming way too lax in giving individual tornadoes article (emphasis mine), followed by them listed two articles (a GA and a GAN) which I created. A brand-new editor should not be that familiar with things, let alone trying to AfD an active GAN two minutes later. This is definitely a SOCK of one of the two weather-sock masters, I just don’t know exactly which. Andrew5 is my gut due to edits like this mentioning policy and things like a behind-the-scenes effort of WikiProject Weather to reassess GA articles. No new editor should even be aware of that process, but Andrew5 100% would and DUCK evidence from previous SOCKs back that idea up. The Weather Event Writer ( Talk Page) 14:29, 6 April 2024 (UTC) reply

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

08 April 2024

Suspected sockpuppets

100.12.36.99's first edits in the last two years was to nominate Elizabeth Leitman for deletion. Majority of their edits in 2022 were weather-related plus an edit on Long Island City (NYC, where Andrew5 is located). Coincidentally, I started this article and Andrew5's latest IPs went on a shpeal about several articles (all of which I started) needing to be deleted. Both this AfD request and the one tried for 2022 Pembroke–Black Creek tornado were posted on Wikipedia talk:Articles for deletion coincidentally a day apart. 174.216.209.32's only edit was to PROD that article. In fact, 174.216.209.32's PROD is the exact same and idential AfD reasoning that 100.12.36.99 put out. Also coincidentally, both of these IPs started edited mere hours after Andrew5 was blocked on 3 IPs. I feel confident on a DUCK report for 100.12.36.99, however, 174.216.209.32 was listed more for future reference of being suspected Andrew5. The Weather Event Writer ( Talk Page) 23:21, 8 April 2024 (UTC) The Weather Event Writer ( Talk Page) 23:21, 8 April 2024 (UTC) reply

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

23 April 2024

Suspected sockpuppets

First edit since 2011 started with “As per usual, WeatherWriter is endlessly yapping” and on Wikipedia:Articles for deletion/2023 Little Rock tornado, where Andrew5 was already blocked once this month. Easy DUCK confirmation. The Weather Event Writer ( Talk Page) 14:57, 23 April 2024 (UTC) reply

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

23 April 2024

Suspected sockpuppets

First edit in 3 years was to revert a strikethrough of a comment by a blocked Andrew5 IP (the other one reported today). Easy DUCK ban. The Weather Event Writer ( Talk Page) 23:07, 23 April 2024 (UTC) reply

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

26 April 2024

Suspected sockpuppets

Only edit in 2024 was to restore Andrew5 SOCK content. DUCK block requested on the IP. User:Colorado is not New York WeatherWriter was added for CU review. The account is currently perm blocked due to username violation, however, this is almost certainly Andrew5 due to what the username is. The Weather Event Writer ( Talk Page) 03:02, 26 April 2024 (UTC) reply

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

11 May 2024

Suspected sockpuppets

Immediately resumed prior behavior for which they had been blocked. Noah, BSBA Talk 15:39, 11 May 2024 (UTC) reply

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

11 May 2024

Suspected sockpuppets

For the 71... IP, it has added trivial content about airport/road closures into recent tornado outbreak/winter storm articles ( here and here), has edited multiple sports-related articles since December 2023, and edited Andrew5's LTA page shortly after attacks took place on Meta, linking to them here. The IP has also edited Wikipedia:Long-term abuse/Samlaptop85213, an LTA page one of his socks created ( here). It has been intermittently active for multiple months in the same topic areas of sports and weather. For the 69... IP, it has edited 2 recent tornado outbreak articles today, and edited several sports-related articles on teams and players in football. His linking to certain policies while making edits, like this one, as well as the particular topics the IP has edited of sports and weather since July 2023 also leads me to believe this is an Andrew5 sock. ChrisWx 🌀 ( talk - contribs) 22:52, 11 May 2024 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • I added 96.57.52.66 for future WP:DUCK reference. Back in March 2024, 71.190.208.91 made reference to a previous WP Weather debate ( Wikipedia:Articles for deletion/List of United States tornadoes in May 2008). 71.190 did not comment in that discussion, however 96.57 did. 96.57 has also coincidentally not edited since January 2024, however, their last edits was on 2023–24 North American winter, which 71.190 edits. Andrew5 is also familiar with winter-storm articles. Also coincidentally, 96.57 and 71.190 never edited on the same day, but seem to edit the same articles (late-December 2023 to mid-January 2024), specifically a lot on that winter article. 96.57 shouldn't be blocked as they are inactive, but noting that DUCK connection for future references.
Also noting 71.190 is picture-perfect Andrew5 sock. Within their last 50 edits, we have sport edits, winter storm edits, hurricane edits, tornado edits, and most importantly, even an edit on WP:LTA/A5, which funny enough is LTA DUCK evidence as Andrew5 is familiar with that specific behind-the-scenes page as well as this SPI page. The Weather Event Writer ( Talk Page) 23:07, 11 May 2024 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

30 May 2024

Suspected sockpuppets

Edit history would suggest this is a WP:DUCK of Andrew5. Between 2023-24, they have made less than 50 edits, consisting of sports (baseball) and weather edits, even on the same day (20 May 2023). This is exactly the lookout on WP:LTA/A5. Coincidentally (DUCK-coincidence), their first edit in several months happen to also be telling others to discount my !vote in a requested move discussion. This is also common Andrew5 behavior, with either personal attacks against other weather editors (plus a few admins) or inserting themselves in discussions in an attempt to say several long-term editors are stupid/irrelevent. Even if they have not edited recently when this SPI is reviewed, if the reviewing administrator feels this is Andrew5 DUCK evidence, I would still appreciate a block or some agreement statement at least, given they are involved in an ongoing RM discussion. The Weather Event Writer ( Talk Page) 09:18, 30 May 2024 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • So um what exactly did Andrew5 do wrong? Those edits look fine, not disruptive, quite helpful and productive actually. Is it just because he’s “socking?” Well, SchroCat blatantly engaged in abusive sockpuppetry but is still allowed to edit. In fact he never had to serve the sanctions that the community decided he deserved. Why doesn’t he get blocked?? Maybe it’s time to realize that Andrew5 is actually an enthusiastic contributor to wikipedia… or else block SchroCat. Can’t be treating certain people differently. Defjotme ( talk) 12:21, 7 June 2024 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

19 June 2024

Suspected sockpuppets

Second IP protested and re-inserted sports-related material that was deemed trivial on June 2024 South Florida floods, two areas Andrew is notorious in. After the first removal, the first IP reverted it again, and then when taken to talk page, the first IP proceeded to argue for its inclusion by mentioning the team names and score. Reeks of WP:DUCK here. Additionally, both added trivial information to Draft:Effects of Hurricane Ian in Florida. -- MarioProtIV ( talk/ contribs) 16:33, 19 June 2024 (UTC) reply

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

Retrieved from " https://en.wikipedia.org/?title=Wikipedia:Sockpuppet_investigations/Andrew5/Archive&oldid=1234197625"
From Wikipedia, the free encyclopedia


Andrew5

Andrew5 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)

03 September 2019

Suspected sockpuppets

Self-admitted and behaviorally similar. Jasper Deng (talk) 20:57, 3 September 2019 (UTC) reply

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

Blocked, tagged, closing.-- Bbb23 ( talk) 21:54, 3 September 2019 (UTC) reply

26 December 2020

Suspected sockpuppets

See below. TonyBallioni ( talk) 13:09, 26 December 2020 (UTC) reply

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

28 December 2020

Suspected sockpuppets

HurricaneTracker and HurricanEdgar had both edited weather related articles, both have similar names, and Edgar has decided to edit Trackers talkpage [1] [2] [3]. Obvious sock is obvious. Thanks. – Davey2010 Talk 11:45, 28 December 2020 (UTC) reply

Comments by other users

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

Cabayi - Ah okay fair point, In this case I may of put 2+2 together and came up with 5. The name, edit area and editing HTs talkpage raised eyebrows but ofcourse I may be completely wrong (which if I am then my apologies). Thanks, – Davey2010 Talk 13:11, 28 December 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  •  Clerk note: I don't find this plausible since TonyBallioni conducted a CU just two days ago and didn't make any comment on this user. Given their shared area of interest it isn't that unusual that Edgar might notice the block & make some edits to Tracker's usertalk. I'll pause before closing in case Tony wants to tell us I'm wrong. Cabayi ( talk) 12:21, 28 December 2020 (UTC) reply
  • Yeah, while it’s not always the case that we get everything in CU, this would have shown up and it didn’t. Closing. TonyBallioni ( talk) 14:26, 28 December 2020 (UTC) reply

28 December 2020

Suspected sockpuppets

User:Andrew5 sockpuppets used this IP to sock and for meatpuppetry ~ Destroyer 🌀 🌀 18:26, 28 December 2020 (UTC) reply

Comments by other users

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

I added more IPs that have been recently abused, within the past month. As well as a range with a history of CU blocks. They are all behaviorally identical, per WP:DUCK. We don't need a CheckUser to publicly link the IPs to the sockmaster, given the obvious behavioral connections. However, given Andrew's history of deception and socking, I would like to request a CU to run a sleeper check on all of the IPs for any new accounts. And any IPs that have been abused by this LTA within the past month should probably be (re)blocked as well. LightandDark2000 🌀 ( talk) 21:15, 28 December 2020 (UTC) reply

Here is some specific evidence pertaining to the remaining IPs that have yet to be blocked: [4] [5]. Here is a confession of sorts (upon closer examination, especially in light of the off-wiki email from Gale5050 to another Wikipedia user on Uncyclopedia, I believe that Andrew was lying and that it was actual socking, not Meatpuppetry). And the block log of the listed /24 range proves the connection to Andrew5. Additionally, a closer look at any edits from any of the IPs on tropical cyclone and highway articles (or any topics in which the socks have overlapping interests) will reveal that they are all essentially the same person. Especially on discussions. Their editing patterns, mannerisms (including difficulty grasping WP policies), and lines of reasoning are all identical. LightandDark2000 🌀 ( talk) 23:49, 29 December 2020 (UTC) reply
I have communicated with Andrew5 on e-mail yesterday and he requested me to show his side of the story in User talk:HurricaneTracker495. But since the page is fully protected, and I did not want to go into trouble trying to get that page edited, I decided to show it here.

I’ll tell you what really happened. My friend, gale5050/Andrew5, told me to do some vandalism on Wikipedia, which I did here. Then they slowly began to get me more into Wikipedia at school which I evantually did, some of my edits were meatpuppety edits but I am a meatpuppet only. I am however, block evading as 2600:387:5:800::/60.

I shouldn’t, but admittedly, we’re both a little hotheaded, meaning we don’t always think before we act. Besides, gale5050 was a very close friend, and in March I was thinking “hey, let’s deface a users talk page!”. I don’t think that way anymore, I’ve matured since, but there is a lot I didn’t know. For example, while I knew they abused wiki data, I was not aware of this blatant harassment. Still, I will agree they have influenced me to (1) make poor decisions and (2) to make me vandalize articles a few times.

In correspondence with him, I'm trying to push him to stop his antics and take a six months away from Wikipedia (to be eligible for taking a standard offer), thus he confessed to me about his actions. Though, it is likely that he's lying to me (based on the his history of lying and deception) about meatpuppetry given he has a control of Gale5050 account on Uncyclopedia. If he's caught sockpuppeting again around this period of time between January to July 2021, I will have a long-term abuse page ready. SMB9 9thx my edits! 00:45, 30 December 2020 (UTC) reply
@ MarioJump83: Gale5050/Andrew5 emailed me on Uncyclopedia, explaining that he was HT495, and in his message welcoming me, he said that he was “that blocked sock”. -Shift 674- 🌀 contribs 20:38, 21 January 2021 (UTC) reply
Gale5050 has been disruptive on Uncyclopedia as well, and his editing is being restricted. Not going into too much detail but many issues (e.g. lying, circumventing blocks/sanctions) have cropped up on Uncyc too. Hipponias ( talk) 11:15, 24 March 2021 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  •  Check declined by a checkuser - I've already looked at all the ranges that the most recent sock was editing on (note; no comment as to if any of the above are them.) Cabayi, mind looking at these for the possibility of blocks? Use your judgement, etc. TonyBallioni ( talk) 01:51, 29 December 2020 (UTC) reply
  •  Clerk note: I can see 67.x is a sock, Special:Diff/993860667, and have blocked for 2 months. Destroyeraa & LightandDark2000, you've obviously seen some evidence - don't be coy, present it. " The truth is out there" isn't enough. Or is it just a shared interest in tropical storms and interstates? Cabayi ( talk) 22:41, 29 December 2020 (UTC) reply
  • A few things. General comment to everyone: this isn't meatpuppetry. Assume good faith isn't a suicide pact so let's not pretend it is here by feeling bad for someone who is lying to us. In cases where there are shared IPs and the like, behavioural analysis matters, and this is very clearly the same person.
    SMB99thx: please don't create an LTA page. They stick out like a sore thumb once you've dealt with them, and the CU log is detailed enough that an open record like an LTA page isn't needed. This SPI should be sufficient for people to report and document, and it's already more active than I would have suspected.
    Destroyeraa: minor procedural note, but typically at SPI, if you're not an admin, clerk, or CheckUser, you comment in the section above and ping clerks/admins/CUs in this section in response, rather than replying directly in the threaded discussion. Not a big deal, but thought I'd let you know for future reference.
    With that, back to Cabayi. TonyBallioni ( talk) 05:55, 30 December 2020 (UTC) reply
  • The remaining IPs are very lightly used in comparison to the 67.x IP. Any further blocks would be punitive rather than preventative. Also, the 170.24.150.0/24 range is held by Nassau County Board of Cooperative Education Services, and cutting off 56 school districts for one infrequent sock is way too much collateral damage. Closing. Cabayi ( talk) 18:21, 31 December 2020 (UTC) reply

28 September 2021

Suspected sockpuppets


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

23 February 2022

Suspected sockpuppets

  Looks like a duck to me Obvious block evasion by the LTA Andrew5. The behavior and areas of interest of these IP socks are identical to those of other IP socks that were blocked earlier this month, such as 69.118.232.58 and 108.170.65.170. This person is editing on the same articles/talk pages as earlier IP socks, as well as similar ones. The articles targeted are all weather articles, especially severe weather/non-tropical storm articles, which he has been very active on in recent months. The similarities include: large-scale intra-wiki copying [6] [7] [8] [9], spamming (often frivolous) renaming requests [10] [11] [12], numerous AfD requests or commenting at said pages (including activity at Wikipedia talk:Articles for deletion) [13] [14] [15] [16] [17], commenting on discussions where other IP socks had previously commented [18], and his condescending, brittle attitude towards other users [19] [20], and similar rationales in RfC votes (compared to earlier socks) [21] [22] [23]. The IP socks merger/deletion rationales are often very similar to the arguments his IP socks made back in late 2020, during the mass merger debacle on the Weather Projects in late 2020, which was one of the main reasons the project implemented a 3-month merger moratorium. Some of the IP talk page activity also resembles that of PlanetsForLife, one of his most recent sock accounts, as seen here [24] [25]. Almost every one of the listed IPs were recently active, especially the last 2, so I strongly recommend blocking each of them. The IPs with more extensive editing activity should receive a longer block. While the last 3 IPs geolocate to Washington State, instead of New York State (Andrew5's known state of residence), I believe that this is due to him utilizing either a VPN or Proxy service, or being on vacation. The behavior from each of these IPs are similar enough to each other and other recently-blocked socks that they're all probably this LTA. I'm also requesting a sleeper check on the IPs, in case he has made new sock accounts for more Extended Confirmed gaming (which he has done before). LightandDark2000 🌀 ( talk) 20:23, 23 February 2022 (UTC) reply

Please do not mass-revert his content additions, as they're actually usually accurate. Even if some of them are unsourced. If his content additions are reverted, they'll have to be readded to those articles again. LightandDark2000 🌀 ( talk) 20:23, 23 February 2022 (UTC) reply
Added some more, based on the admission. Please run a check on the user account and the IPs. The user account also needs to be indeffed. LightandDark2000 🌀 ( talk) 21:45, 23 February 2022 (UTC) reply

Comments by other users

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

(on a different IP) Ok, I’ll admit it. I am block evasion on Wikipedia. But please please hear me out. First of all, Humiebees is not me and we have totally different interests, and the Phoyner accounts was indeed my friend. Also, PFL isn’t me. But those IPs are. I figured if I wasn’t going to get unblocked, that I should still help out Wikipedia. I wanted to improve Wikipedia even though I knew I couldn’t. So I made massive edits to Wikipedia articles to try to improve the site, make it more comprehensible to readers and to just make Wikipedia Storm articles better in coverage. I want to thank LightandDark2000 for crediting me to my public contributions, and for asking them to not mass revert my contributions. I am not using a VPN, I used multiple public IPs in New York, and then took a trip to Washington. I have used other IPs as well I will disclose shortly, but I did all of this to try to improve Wikipedia. These storm damage estimates I am adding in at a serial rate allows people to know the true cost of these storms, and that’s just one of the things I did. I really regret all the sins I have done to Wikipedia, because I really just messed up everything. @ Bbb23:, I am truly sorry for sending you that threatening email, I was simply in the moment and couldn’t think straight. I could’ve had such a nice future on Wikipedia, and I threw it away. I know I will not be unblocked, but can I at least have a standard offer attempt where I can then be unblocked? I really mean what I said that I can become a productive Wikipedian, because I think I have demonstrated that. 65.144.40.106 ( talk) 21:15, 23 February 2022 (UTC) reply
As I compile a list of other IPs I’ve used (104.246.113.199, 160.72.80.50 are the two I found so far), I want to make a note that many of them are public, the Washington IPs I will be leaving the state tomorrow, and the 4th IP from bottom belongs to JFK Airport, so please keep that in mind when blocking. 65.144.40.106 ( talk) 21:22, 23 February 2022 (UTC) reply
There were a few Wikipedia accounts I used in the last little bit, but the only one I remember using was 4WeatherNerd. I’ll look through some histories and find others. 65.144.40.106 ( talk) 21:30, 23 February 2022 (UTC) reply
Although stale, I do remember using TornadoFan45 and 50.74.160.74. Back then I was using the unreliable DailyRecord, recently to be more reliable I switched to NOAA’s official Database. 65.144.40.106 ( talk) 21:37, 23 February 2022 (UTC) reply
Your only chance at a Standard Offer is to go 6+ full months without any socking or editing anywhere. Actually, with your level of socking, you'd probably need a minimum of 12 months without socking before Stewards would be willing to Unlock your main account. And you'd also have to explain your abusive behavior, including various personal attacks and Anti-Semitic comments that came to our attention over the last year. An apology would be necessary at a minimum, but with this extent of abuse, it would be extremely difficult for you to be allowed back, if ever. You've burned down nearly all of your bridges at this point, and if you continue, it's very likely you'll never be welcomed back. LightandDark2000 🌀 ( talk) 21:45, 23 February 2022 (UTC) reply
When have I ever made anti-Semitic comments? I am a Jew myself. I believe the comment I made, was that Ghana wasn’t notable, and I’m sorry for this because I know I insulted a lot of people not just from Ghana, but from Africa. Also, personal attacks have been one area I have been trying to avoid. I just feel terrible making them, so I’m sorry for any I have made because I never intend them as such. Also, I find it too hard to stay off Wikipedia. From February to October, I didn’t make any edits because I am not PlanetsForLife, it was just someone who had the same interests as me in the same area, and the IP must’ve started to edit a day after I was blocked (a tragic coincidence). I just need to become more mature. I swear it’s just too hard to hold down these temptations. That’s why I made the accounts, I literally couldn’t hold back my temptation to edit but couldn’t wait until I could go back to a public IP address, as I didn’t want to out 67.185.37.186 was still my IP (maybe I mistyped it, it’s very prolific). I know this is not going to get me unblocked, I just wanted to get my story out there when I had the chance. 65.144.40.106 ( talk) 21:52, 23 February 2022 (UTC) reply
I also understand it will take 6+ months and in my case could take a year (hence why when I applied after only 6 months, it was declined, both at WP:UTRS and ArbCom), but I was wondering if something like 8–10 would be sufficient. I swear, it’s just that the longer I have to wait, the more likely it is that I slip up, and the reason I began socking in the first place was, and it was the worst thing I could’ve done and i’m sorry for it, was because I realized what’s the point of waiting 6 months, having it denied, then finding another account, I just figured IP block evasion is easier if no one knew. And no one found out for over 3 months, and had I not returned to my old ways, no one would have found out. So L&D, I’m sorry that I did that because not only did I probably hurt your feelings, but it also caused everyone to find out. I shouldn’t have gotten so cocky when I went to Washington but then again, I just shouldn’t have block evaded. I know I shouldn’t even be editing, but I just thought it would be better for me if I apologized now. Also because this is a public IP, I will never be editing from here, and t after tomorrow I will not have access to the 12 IP, the 209 IP and the 198 IP and the other from Washington. So please don’t block those for more then 31 hours. 65.144.40.106 ( talk) 22:03, 23 February 2022 (UTC) reply

My initial reason I did the socking was because I didn’t know socking was banned until February 2020. When I created Andrew5 and Guttmana9 I thought it was ok to do one on phone and one on computer but I was wrong. (My first edits to Wikipedia were on 47.16.99.72 in April 2018, this was a year after that but that IP was since relocated and hasn’t been used since the global block expired in November 2020.) and because I got no block notice, I didn’t know how to appeal it, hence me using UTRS. I still didn’t know with ImtheOneKhaled and didn’t get to the SPI in time, so even in September I didn’t know. Now, I know I have to justify my socking since then, I just thought I could try to make the encyclopedia better. From interstate articles, shifting over to weather during September (I got interested mainly because of Hurricane Laura), and because my IP shifted due to Hurricane Isaias knocking out the power, I had a chance. I wanted to do everything my I could to not get caught, but I clearly failed at it. And all these socks that aren’t even mine just mean I have to wait even longer to get unblocked. PFL likely ruined my standard offer attempt that I made. When i used 69.116.96.17, and all the edits got reverted I thought they found out, but I should’ve stopped when the initial block of 98.116.15.128 (or whatever) was placed. But I chose not to, and now I have to live with the consequences. Because the other school IP was blocked, this means no one at school could edit Wikipedia. Also, some other accounts and IPs I remember using now were 24.189.217.187, Blizzard45678, 67.82.182.94 and 70.23.39.2. I am listing IPs that are stale because I will need to do so anyway when I take on the standard offer, so I am doing it know to get the admission out of the way. 209.201.121.4 ( talk) 13:27, 24 February 2022 (UTC) reply

I will never be editing from this IP again due to me leaving Seattle. Good bye. 209.201.121.4 ( talk) 13:53, 24 February 2022 (UTC) reply

Also please don’t block this IP, it belongs to the airport at Seattle and I will be leaving it for a flight extremely shortly. That being said, I did use 209.53.224.34 while I was in Vancouver, but as I am going to the east coast please don’t block it as it belongs to an aquarium. 198.134.98.50 ( talk) 16:19, 24 February 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

12 August 2022

Suspected sockpuppets

I am not an expert in storm socks, but the above users appear to be all the same as each other, and I've seen some intersection with socks of Andrew5, so I figured this was the best place to file this. Similarities: (1) usernames, (2) recent accounts, (3) no special tags for editors or platforms, and (4) they don't act like new accounts, i.e., knowing templates and hats I'd never even heard of (broader instead of main). Bbb23 ( talk) 20:30, 12 August 2022 (UTC) reply

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

24 October 2022

Suspected sockpuppets

Started editing today and one of their first edits was on Talk:Tornado outbreak of December 10–11, 2021 to propose a split, which was previously proposed by a blocked sock (47.16.96.33) last month, with the exact same reasoning. They also have only edited weather-related articles, which the previous sock did as well. Confusing chain of sock references that go through like 4 different accounts, so I put Andrew5 as well, but I am unsure if that is the main/first sock account of this editor. Direct correlation to 47.16, which was confirmed as a sock. Elijahandskip ( talk) 17:15, 24 October 2022 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
Just knowing about a discussion doesn’t mean I’m a sock. However I was admit I was informed of this by off wiki means. 173.68.1.128 ( talk) 17:44, 24 October 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

01 November 2022

Suspected sockpuppets

69.118.235.133 & 71.183.166.47 both edited a split proposal on Talk:Tornado outbreak of December 10–11, 2021 as their 20th edit and 1st edit on Wikipedia, respectively. The split proposal has been proposed twice by the same sock master (Under User:47.16.96.33 and User:173.68.1.128) and all four accounts (two blocked and two new suspected) have an interest in weather.

170.24.150.2 gave weird vibes to myself and United States Man (Extra off-SPI discussion here) as they started editing weather-articles 4 days ago (October 27th) and suspiciously, the last blocked account of the sockmaster was 173.68.1.128, which was blocked the day after this account started editing (but three days before the blocked account (173.68.1.128) messaged in the SPI after being suspected/accused of it.) Suspecting all three are potentially the same editor as none of them have edited on the same day and all have an interest in weather articles and they all never edited the same day as the previous blocked sock (173.68.1.128). Elijahandskip ( talk) 03:58, 1 November 2022 (UTC) reply

Comments by other users

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

There have been quite a few cases of an apparent IP-hopping editor on tornado-related articles and their talk pages. It has been going on for a while. One aspect of these IPs that first jumps out is their behavior indicates knowledge of the workings of Wikipedia beyond what would be expected of a new editor. Other traits, that have led me to, at times, suspect these IPs are Andrew5 are often confrontational attitudes, and frequent allusions to Wikipedia policy and guideline pages. 47.21.202.18 ( talk · contribs · WHOIS) seems to have been the most frequent ones that come up. I know this is old evidence, but in once such instance 47.21.202.18 added a section to Tornado outbreak of March 5–7, 2022. After that was reverted 69.116.96.17 ( talk · contribs · WHOIS) then readded the section with accusations of WP:STATUSQUOSTONEWALLING and brought the matter to ArbCom. While this would normally be considered stale, I'll note that both IPs have continued to edit many of the same weather-related articles. This is mainly to establish the continuing trend of IP-hopping. More IPs may need to be added in the near future. Honestly, this sort of pattern of an IP-hopping editor, up to and including recent comments at Talk:Tornado outbreak of December 10–11, 2021. This user has basically admitted to IP-hopping in the past, as at Wikipedia:Sockpuppet investigations/Andrew5/Archive#23 February 2022. TornadoLGS ( talk) 04:51, 1 November 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

I'm confident all the IPs mentioned are Andrew5. Due to differing stability:

Closing. DatGuy Talk Contribs 07:28, 1 November 2022 (UTC) reply

02 November 2022

Suspected sockpuppets

170.24.150.113 has confirmed via Wikipedia:Articles for deletion/2012 Henryville tornado that it is a school IP address on Long Island, while WHOIS confirms the other IPs are all from the same place on Long Island or Virginia (locations of previously blocked IPs). Each new IP address tries to act like a different person, trying to make it seem like a coincidence that multiple anon users all pop up in the same place at once with the same agenda, same general in-depth knowledge of Wikipedia, and same general attitude. Several other IP addresses were just blocked a couple days ago for the same odd behavior at the same weather articles. Elijahandskip and TornadoLGS have both had encounters with this situation and may care to comment here.

The previously blocked IPs are 170.24.150.2 ( talk · contribs · WHOIS), 71.183.166.47 ( talk · contribs · WHOIS), 69.118.235.133 ( talk · contribs · WHOIS), 47.21.202.18 ( talk · contribs · WHOIS), and 69.116.96.17 ( talk · contribs · WHOIS). It is suspected that all of these accounts are the same person, despite trying to act like different people, given very similar behavior in the same place at the same time. United States Man ( talk) 23:06, 2 November 2022 (UTC) reply

Comments by other users

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

I'll note that most of the listed IPs have shown an interest in the newly created article 2012 Henryville tornado and, despite claims to the contrary, it seems unlikely that a bunch of people would suddenly start editing Wikipedia for the first time upon hearing about a newly created article about an event that happened ten years ago. TornadoLGS ( talk) 01:03, 3 November 2022 (UTC) reply

Really? This is a public IP,hence the collusion makes sense. Some of these IPs really have no evidence. The 148 IP, really? Attribution is in the TOU, and AFC is the only way for IPs to create articles. 71 seems to be no evidence. And making every IP working to save Henryville to get it deleted is a witchunt. -- 170.24.150.113 ( talk) 11:19, 3 November 2022 (UTC) reply
I'll elaborate, since classes cut me short. What I mean is, even if it's unlikely that all the new accounts would gravitate towards the article, WP:AGF prevents us from assuming that it is the cause without more concrete evidence. -- 170.24.150.113 ( talk) 12:03, 3 November 2022 (UTC) reply
The same general knowledge of the same events and the same knowledge of WP policies and guidelines despite not being an autoconfirmed user point to the fact that all of these are the same person. Not to mention the fact that previously blocked socks have come from the same addresses. The only defense from the accused points just sounds like grasping at straws. United States Man ( talk) 18:32, 3 November 2022 (UTC) reply
Adding to USMs comment, this all fits the pattern of previously known socks. WP:DUCK applies. TornadoLGS ( talk) 20:55, 3 November 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

30 November 2022

Suspected sockpuppets

170.24.150.113 is a confirmed sock of Andrew5 that is continuing to be allowed to edit freely on Wikipedia, thus making a complete mockery of this entire process. @ TornadoLGS and Elijahandskip: can testify to this as well. United States Man ( talk) 19:06, 30 November 2022 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
How dare you make this accusation. Aggressive Wikipedia users are quite common, you are one yourself.-- 170.24.150.113 ( talk) 19:06, 30 November 2022 (UTC) reply
It's not an accusation. An admin confirmed it in a previous report lol. United States Man ( talk) 19:07, 30 November 2022 (UTC) reply
No they didn't. Quit being a brat.-- 170.24.150.113 ( talk) 19:08, 30 November 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

4 December 2022

Suspected sockpuppets

Previously blocked socks of Andrew5 that are continuing to be allowed to edit freely on Wikipedia, thus skirting around the sockpuppet process. I suspect there are more IPs around in which the user edits the same types of articles and displays the same editing characteristics and abrasive behavior toward others. WP:DUCK applies in those cases. United States Man ( talk) 20:45, 4 December 2022 (UTC) reply

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

13 December 2022

Suspected sockpuppets

Three different IPs making the same edit with the same argument at Hurricane Isaias. The different IPs are an attempt to skirt the 3RR or to sway talk page discussions and has been done multiple times with previously blocked socks. These IPs routinely edit the same types of articles and generally perform the same types of edits. The fourth and fifth make similar edits as well. WP:DUCK applies here. The WHOIS addresses all point to the same town (and many cases, same address) on Long Island, or towns immediately adjacent. Most previously blocked IP socks of Andrew5 have this address (or town) in common. United States Man ( talk) 06:32, 13 December 2022 (UTC) reply

Comments by other users

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

Given our issues of playing whack-a-mole with IPs, I suggest page protection on this case. TornadoLGS ( talk) 20:04, 13 December 2022 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

15 December 2022

Suspected sockpuppets

This group of IPs is continuing in the same pattern as previously observed by Andrew5 socks. This includes editing (including edit warring) across multiple IPs, a confrontational attitude when edits are reverted or criticized, and a focus on storm-related articles. The most recent activity has involved edit warring at 2010 New Year's Eve tornado outbreak ( [26]], [27], [28]) and Hurricane Isaias tornado outbreak ( [29], [30], [31]). See also those page histories and IP talk pages. Other IPs were mentioned at the previous opening of this case. It seems saying "How dare you" has become a calling card of theirs. In an earlier report here, the closing admin RoySmith opted for page protection since this person seems to change IPs faster than they can be blocked, but stated: If that proves ineffective, we can look at stronger measures. I'm not sure what that would involve. This person has been on quite a few weather articles. TornadoLGS ( talk) 22:14, 15 December 2022 (UTC) reply

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

17 January 2023

Suspected sockpuppets

[32] [33] [34] 3 complete almost duplicate comments on a weather-related article. When asked to start a discussion about it, instantly went and started a noticeboard, which has been the behavior of this sockmaster who likes to escalate issues. 69 started editing weather articles on January 6 then stopped until January 10, then stopped until January 17. None of the three accounts edited at the same time. Based on the behavior, talking about “core policies” and such (similar to the Aon/NOAA debate which had multiple sock accounts from this sockmaster & bring it straight to ArbCom)… WP:DUCK applies here. Elijahandskip ( talk) 21:54, 17 January 2023 (UTC) reply

Comments by other users

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

Adding to this report 69.127.228.206 ( talk · contribs · WHOIS) and 47.19.209.232 ( talk · contribs · WHOIS) have both engaged in a small revert war at Tornado outbreak of December 10–11, 2021, showing the same confrontational attitude and pattern of IP-hopping as is typical. Both of these IPs appear similar to ones previously used by Andrew5. Filing a report at an Andministrative noticeboard is also consistent with past behavior. Previous closing admins have mentioned page protection as a remedy. TornadoLGS ( talk) 22:53, 17 January 2023 (UTC) reply

Page protection is not a remedy because said IP addresses continue to edit other articles. The best remedy would be to block the IPs so a sockpuppet isn’t allowed to freely edit Wikipedia and flaunt the whole sockpuppet idea and process. United States Man ( talk) 13:58, 18 January 2023 (UTC) reply
This, to me, seems like an attempt for WP:WEATHER to gain an edge in a dispute. Firstly, let me say there was a flaw in the filing - the ArbCom filing seemed to have not been over NOAA/Aon drama, but rather over whether or not a section could be added to Tornado outbreak of March 5-7, 2022. Elijahandskip is trying to own the template for the deadliest events in 2023 and is inserting WP:OR into the article. Important point to note - I didn’t even bring it up to the notice board for even me! I brought it up to the noticeboard because someone else noticed it! Are we now going to file an SPI on them because of that? i thought not. So this seems to be a bias against IP editors. Truly shameful. TornadoLGS, Elijahandskip, USM, ChessEric and Poodle23, amongst many others, have been treating IP users as less to regular users, and frequently look for a way out. As can be seen in the previous SPI, only 2 IPs since November 2 have been blocked. One were previously blocked, and the other deserved a block for egregious WP:NPA violations. That entire range is now blocked. The evidence seems to be grasping at straws as a way to “win” the debate, and this behavior from the WikiProject is unacceptable and is why they are in so much trouble to begin with. Additionally, as this IP belongs to a synagogue, this appears to be antisemitism as well. 69.127.228.206 ( talk) 20:25, 18 January 2023 (UTC) reply
Now that last comment seems to be so much speculation and extremely judgemental, especially since every user you just mentioned is a 100% separate user & deals with multiple users who edit under an IP. But are you saying the other two IP’s listed in this are not you? If so, then why was the comments almost duplicate (including the 2nd comment even saying “still”, indicating it was the same person as before? Also, I think your “I didn’t even bring it up to the notice board for even me! I brought it up to the noticeboard because someone else noticed it!” is a direct admission of multiple users on the same account. The way I read that, you said a user was on that IP at 21:17 on January 17 on a talk page and a 100% different user was on the account at 21:30 on January 17 who created the IP & who just happened to continue the exact same discussion? To answer your other question, I wouldn’t have even thought about starting an SPI until I saw three unique IP accounts, following the same pattern that has been seen on multiple weather-related articles since July 2022. Admins have even confirmed multiple users (most pre-November 2022) as being the exact same person. If you are not connected to any of the other users, then you wouldn’t be blocked. That simple. But the editing pattern almost speaks for itself, unless it is an exceptional coincidence. Elijahandskip ( talk) 20:40, 18 January 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Blocked IP 69.127.228.206 for two weeks. The other IPs haven't edited recently enough to bother. There is a tremendous amount of IP hopping in this case and it's unfortunately hard to do much about it. Closing. Bbb23 ( talk) 20:44, 18 January 2023 (UTC) reply

6 February 2023

Suspected sockpuppets

I may be jumping the gun, but this revert edit is similar to what I've seen in the past with AON/NOAA disputes, especially since different IPs doing the reverts seem to be the norm. Please look into this. Thanks. ChessEric ( talk · contribs) 22:07, 6 February 2023 (UTC) reply

I thought I'd thrown in a second IP as well. The IP was in the last investigation, but was not blocked due to a lack of recent edits. However, editing on this account returned the day after the investigation was closed and it had an aggressive tone that I've seen in the past. I looked back through the edit history and found some similar patterns to past socks (i.e., [35], [36], and [37]). Please look into these. Thanks. ChessEric ( talk · contribs) 22:52, 6 February 2023 (UTC) reply

Comments by other users

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

The WHOIS location and edit history of this account match similar blocked accounts as well. United States Man ( talk) 22:20, 6 February 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

23 February 2023

Suspected sockpuppets

1st IP appears to have been caught by United States Man, so I bought it here. This edit ( [38]) appears to have been a follow-up to this one ( [39]) as well and Andrew5 has been known to use multiple IP addresses for edit warring. The 2nd IP has been in the last two investigations and appears to start editing only after the investigations conclude. Please look into these. Thanks. ChessEric ( talk · contribs) 18:50, 23 February 2023 (UTC) reply

I just added a third IP whose WHOIS matches Andrew5. They apparently didn't like this revert I did, so they reverted me and left me this warning on my talk page. I will admit it gave me a good chuckle this morning, especially since the revert I did said nothing about the IP being a sock. Anyway, please look into these. Thank you. ChessEric ( talk · contribs) 16:40, 24 February 2023 (UTC) reply
I just nabbed a 4th IP that has the same WHOIS as the 2nd one. I'm having a little too much fun confronting him though; I'll try to tone it down so I don't break any rules. ChessEric ( talk · contribs) 22:34, 25 February 2023 (UTC) reply
Found a 5th IP who commented in this discussion. The WHOIS matches the 2nd and 4th IPs. ChessEric ( talk · contribs) 15:26, 26 February 2023 (UTC) reply
6th IP's WHOIS matched 2nd, 4th, and 5th. ChessEric ( talk · contribs) 15:28, 26 February 2023 (UTC) reply
8th, 10th, 11th, and 12th IP's WHOIS match other ones on this list. The 8th and 9th ones don't, but their both located at the same place in Colorado, so something is going on with those 2. ChessEric ( talk · contribs) 15:41, 26 February 2023 (UTC) reply
Actually, I'm a bit confused now. The Ashburn location is a Verizon building ,so why are there so many accounts out of there? Is it like a centralized tower or something? ChessEric ( talk · contribs) 20:04, 26 February 2023 (UTC) reply
Just added a new one with a matching WHOIS. ChessEric ( talk · contribs) 23:03, 1 March 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • Uh…I don’t even know what to say. Is there something going on, because I don’t know what any of this is. 98.116.45.220 ( talk) 19:45, 26 February 2023 (UTC) reply
  • WHOIS evidence isn’t enough in an SPI case. In this case, right at the top of WP:SPI, it says Evidence is required. When you open the investigation, you must immediately provide evidence that the suspected sock puppets are connected. The evidence will need to include diffs of edits that suggest the accounts are connected. (This requirement is waived if the edits in question are deleted; in this case just provide the names of the pages that the accounts have been editing.) You must provide this evidence in a clear way. Vaguely worded submissions will not be investigated. You need to actually show why your suspicion that the accounts are connected is reasonable. Concision is key. Evidence should be presented in a concise format. Because of the length of the backlog, cases with clear and concise explanations and evidence are handled the most quickly. ChessEric has provided very few diffs and just gave WHOIS evidence. However, (1) WHOIS isn’t always right, (2) this is a very densely populated area (Long Island) and comes from different organizations, and (3) we seem to only be served by a few towers. Also, ChessEric seems to be opening a WP:WITCHHUNT for paranoia reasons to get IPs out of WP:WEATHER. That isn’t allowed. 71.125.62.146 ( talk) 21:25, 3 March 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

2 March 2023

Suspected sockpuppets

I know the previous case just closed, but I found another IP whose WHOIS popped up as a common Andrew5 location. He seems to be keen on putting records ( [40]) into articles and that's what tipped me off here. Additionally, this IP has previously said that they wanted me topic-banned from the weather project based on the canvassing issue that occurred on February 9, although my ban was for threats of violence, which I do regret. Regardless, the IP appears to be a repeat offender of Andrew5. Please look into this. Thanks. ChessEric ( talk · contribs) 23:10, 3 March 2023 (UTC) reply

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

8 April 2023

Suspected sockpuppets

IP addresses of Andrew5 have been repeatedly trying to make the WP:Weather a contentious topic, which leads up to this edit not too long ago. It was completely off-topic and unnecessary. I've been keeping my mouth shut about these, but I'm tired of seeing this so I want one of IPs nipped in the bud. Thank you. Chess Eric 22:21, 8 April 2023 (UTC) reply

Comments by other users

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

Added two more from Talk:1932 Deep South tornado outbreak, where both IP addresses employee the same behavior and edit history (along with WHOIS location) as many other instances of Andrew5. United States Man ( talk) 19:37, 9 April 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

27 May 2023

Suspected sockpuppets

98.113.8.17, 69.118.237.29, and 47.19.209.230 matches the most recent editing pattern for 98.116.45.220, a recently suspected sock: Weather and baseball (looking at most recent 50 edits for all accounts show that). They all match the most recent blocked sock as well 71.125.32.0/19 with weather and baseball. While 47.19.209.230 and 69.118.237.29 have not edited recently, they all commented in a discussion. Confirmation of if they are or are not a sock is requested to know of the discussion was sock stacked or not since 3 of the 5 editors involved seemed to match the sock’s editing pattern. Possibly WP:DUCK. Elijahandskip ( talk) 16:11, 27 May 2023 (UTC) reply

  • I just added 75.99.68.66 to the list as well. Edited recently dead match with the others with baseball and weather interests in the last 20 edits. Very clear WP:DUCK from the ip-hopping sock master. Elijahandskip ( talk) 00:17, 28 May 2023 (UTC) reply
    I just added a fifth one, 216.165.125.249, as well. Dead match with multiple weather and baseball related edits on July 12 (see contributions). Noting, the commented in an ongoing merge discussion that affects 3 articles, so if they are a sock, a block or at least confirmation is needed. The Weather Event Writer ( Talk Page) 00:20, 13 July 2023 (UTC) reply

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

30 July 2023

Suspected sockpuppets

71.125: WP:DUCK match in contribution history of weather-related edits and baseball edits (see contribution history for July 16 & 30, 2023). 98.166 was found after looking through the 2023 Chicago Cubs season article, which both accounts edited. July 23 and July 16 (right before the 71.125) contribution histories are WP:DUCK matches as well. Noting that 71.125.36.50 Was previously blocked on WHOIS evidence and then appealed saying, “Way too many of these Nassau County IPs have been blocked over the past 3 years. We just want some stability”, which is basically a SOCK confirmation. Can the IPs be perm blocked given multiple day usages and usages after the previous block as well? The Weather Event Writer ( Talk Page) 15:31, 30 July 2023 (UTC) The Weather Event Writer ( Talk Page) 15:31, 30 July 2023 (UTC) reply

Noting I have added 104.246.113.199 & 72.68.134.254. 104.246.113.199 Edited again on July 19, 2023 (after IP sock block — See their contribution history). 72.68.134.254 was discovered through WP:DUCK editing on Draft:January 2023 North American storm complex, which numerous IPs linked to this sockmaster have edited. Maybe an SPI investigation into all the IPs that have edited the draft should be looked at. No solid reason newer IPs (i.e. 72.68.134.254) should be edited a draft, which is basically only IP edits in the last 6 months. Strong WP:DUCK connection. The Weather Event Writer ( Talk Page) 23:15, 31 July 2023 (UTC) reply
69.119.89.11 was added as a WP:DUCK match (Weather and baseball edits) on the same days on July 15 and 22. The Weather Event Writer ( Talk Page) 23:34, 31 July 2023 (UTC) reply

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

11 August 2023

Suspected sockpuppets

See contribution history with a WP:DUCK match of weather and baseball edits on the same day. Also, they were previously blocked on this IP address (February 2023) and continued editing on it, so this may deserve a perm block for the IP. The Weather Event Writer ( Talk Page) 22:57, 11 August 2023 (UTC) reply

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

11 August 2023

Suspected sockpuppets

WP:DUCK, matching baseball and weather edits on the same day, seems like Andrew5. Baseball edit here, the weather edits are on this page's history. Tails Wx 02:46, 12 September 2023 (UTC) reply

Also throwing in 75.99.8.58 for match of weather and baseball edits as well. Tails Wx 00:48, 24 September 2023 (UTC) reply

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

12 October 2023

Suspected sockpuppets

WP:DUCK confirmation on October 12, 2023 (Baseball and weather (winter storm article) edits within 4 minutes. This sock account was used previously on June 14, 2023. Can we seriously just start perm blocking the IPs? This has been going on way too long, taking up the time of editors and administrators practically every month. The Weather Event Writer ( Talk Page) 18:57, 12 October 2023 (UTC) reply

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'm not willing to block indefinitely, but I'll be likely to consider longer blocks moving forward. I sampled some of the IP socks in the archive and am not seeing any evidence that lengthy blocks will cause much collateral damage. This ducky IP is blocked for a year. Closing. Firefangledfeathers ( talk / contribs) 03:59, 14 October 2023 (UTC) reply

29 October 2023

Suspected sockpuppets

Otis2023 made 3 edits (their only 3 edits on Wikipedia) on October 27 to Draft:Hurricane Calvin (2023) and Draft:Tropical Storm Sonca (2022). ThatBigSwiftie1989 made 2 edits (their first two edits) to the same draft articles. Edits on Hurricane Calvin’s draft are identical [41] [42]. Either SOCK inventions or accounts needing to be linked together in some fashion. Given the identical comments in an AfC, there may be some SOCK master before Otis2023, since they have knowledge of at least 2 draft articles as well as how to make AfC comments. Thought, this may be User:Andrew5 alts (unsure), since Andrew5 (sock master) likes to edit winter weather articles and ThatBigSwiftie1989 made their 3rd/4th edit on two winter articles within minutes of starting to edit. The last Andrew5 confirmed alt, User:108.54.87.90 edited winter storm articles as well, so a location-check is probably needed to verify if it is Andrew5. The Weather Event Writer ( Talk Page) 21:22, 29 October 2023 (UTC) reply

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

Dreamy Jazz talk to me | my contributions 22:50, 29 October 2023 (UTC) reply

04 November 2023

Suspected sockpuppets

Their only edits today was to nominate Hurricane Calvin (2023) for deletion with the exact same reasoning as their other SOCK accounts gave to prevent it being accepted at AfC (which it was). WP:DUCK/suspected sock confirmation edits: Sock 1, Sock 2, Suspected Sock. The Weather Event Writer ( Talk Page) 15:33, 4 November 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
And too bad you can’t use CheckUser to find out. Maybe Lidia2024 and Andrew5 are the same user also. 69.118.232.58 ( talk) 19:50, 4 November 2023 (UTC) reply
  • @ WeatherWriter: I just checked the block logs of the IP's, and all of them you listed were previously blocked as sockpuppets as early as January, with the third one's previous block actually mentioning Andrew5. I also wanted to mention the DamageReportAdder account, who added damage totals with non-NOAA sources such as Aon to Tornadoes of 2023 and other pages, which I noticed that he has a history of doing with previous IPs/accounts. ChrisWx 🌀 ( talk - contribs) 02:07, 5 November 2023 (UTC) reply
    Lol the evidence for accusations seems to be really really really really really low. Aon? Really? Are you about to call Destroyeraa an Andrew5 sock because they used Aon? Or HikingHurricane? Besides, the original accounts behind the Aon debate geolocated to South Carolina, Texas and Arizona, whereas Andrew5’s known state of residence is New York, with his only known vacation being made to Virginia and the Pacific Northwest. The bar is really low for evidence for IPs, yet when the exact same evidence is filed against an experienced editor, all of a sudden it is discarded. This seems like a violation of WP:5P4.-- 69.118.232.58 ( talk) 14:23, 5 November 2023 (UTC) reply
    Also noting that the DamageReportAdder account's only purpose seems to be to add Aon to weather-related pages, here's an example of previously blocked Andrew5 sock doing so, then reverting back to it with an argumentative tone. It's entirely possible that the DRA account is someone who wasn't aware of the NOAA damage precedent trying to add the totals in, but I'm mentioning it because it seems suspicious. As for Destroyeraa and HikingHurricane, they have a very different editing style, the edits were before its reliability was established, and simply citing an edit or two of theirs does not prove that they are socks. ChrisWx 🌀 ( talk - contribs) 16:04, 5 November 2023 (UTC) reply
    Citing one or two edits worked for many Andrew5 IPs in the past, check the archive. 69.118.232.58 ( talk) 21:32, 9 November 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

21 November 2023

Suspected sockpuppets

User copied content from the talk page of a recently blocked IP address ( [43]) and edited weather/sports edits on the same day as that copied content (which was weather-related): sports/ weather 1 & weather 2. WP:DUCK reasoning seems strong and the blocked IP which had content from their talk page copied by this user admitted in a ban appeal less than 48 hours ago to editing on multiple IP addresses. Checkuser is requested strictly on WP:DUCK evidence. The Weather Event Writer ( Talk Page) 23:55, 21 November 2023 (UTC) reply

Also noting this user was previously blocked in 2022 for a year for block evasion, which also supports a WP:DUCK check, given the connection to a recently blocked account. The Weather Event Writer ( Talk Page) 05:23, 22 November 2023 (UTC) reply

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

26 November 2023

Suspected sockpuppets

Typical WP:DUCK evidence in their edit history (Weather/baseball). They also basically confirmed they are a sock by reverting admin @ K6ka: on Talk:San Francisco–Oakland Bay Bridge, who reverted a now blocked SOCK (71.125.62.208), who was causing disruption and edit warring on the page. I'm assuming Andrew5 is the master given the weather/baseball history, but K6ka knowns the sock master as they blocked this sock earlier today. The Weather Event Writer ( Talk Page) 00:06, 26 November 2023 (UTC) reply

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

26 November 2023

Suspected sockpuppets

Check edit history. IP re-engaged in the exact same four edit warring discussions as the previous IP, including reverting the blocking admin who did a SOCK-disruption revert on Talk:San Francisco–Oakland Bay Bridge. Also a fun SOCK confirmation saying “stop bribing admins to block innocent IPs. This is a violation of WP:PAID”. The Weather Event Writer ( Talk Page) 17:22, 26 November 2023 (UTC) reply

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

06 December 2023

Suspected sockpuppets

After not editing for a month, their third edit was to re-revert something previous Andrew5 SOCKS were reverting. The previous user to revert this was 47.21.202.18, who was blocked for 2-years as Andrew5. Also, the user who reverted it prior to 47.21.202.18 was 47.23.6.178, who was also blocked as Andrew5. Unlike other times, this is all I have (not solid WP:DUCK evidence), which is why checkuser is requested to see if this is Andrew5, or a separate editor. The Weather Event Writer ( Talk Page) 15:53, 6 December 2023 (UTC) reply

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

WeatherWriter, CheckUsers will not, for privacy and policy reasons, publicly divulge a connection between a registered user and an IP. IP socking reports are made or broken on behavioral evidence. A clerk will likely be by soon to decline the CU request. I'm inclined not to block based off of the edits so far. I'll keep an eye on them; you should too. Firefangledfeathers ( talk / contribs) 16:07, 6 December 2023 (UTC) reply

11 December 2023

Suspected sockpuppets

First edit ever was to re-create Draft:Late October 2012 North American blizzard, which was deleted earlier today for being created by a Andrew5 sock. The Weather Event Writer ( Talk Page) 19:41, 11 December 2023 (UTC) reply

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

12 December 2023

Suspected sockpuppets

Most of these IPs have already been previously blocked as Andrew5 socks in the past, but they have edited since their block has expired with similar behavior to their socks, such as their interest with the Northeast United States, including Long Island, in their weather-related edits, editing their usual targets, such as Tornado outbreak of December 10-11, 2021 (removing size tag, previous socks have gotten into similar conflicts on page), and addition of snow/rainfall records on pages, which is common sock behavior for Andrew5. Some IPs haven't edited in multiple days, but since they usually edit on static IPs, they will still need to be blocked for a long period of time. A rangeblock may also be needed since they are likely on similar ranges. If there are any problems with this, please let me know. Thanks, ChrisWx 🌀 ( talk - contribs) 02:08, 12 December 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • I am not sure about the other three, but 69.116.96.17 is Andrew5 per their November 2022-23, 1 year ban-evasion block. Disruptive or not, that account in edit on November 26, 2023 and Andrew5 obviously is still blocked. So 69.116.96.17 for sure needs a new ban-evasion block (2 years like the other SOCK accounts). The Weather Event Writer ( Talk Page) 02:14, 12 December 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

13 December 2023

Suspected sockpuppets

Blocked before as a sock of Andrew5 and immediately went to edit the draft of TS Bret where the socks from yesterday were editing. Noah, AA Talk 14:08, 13 December 2023 (UTC) reply

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

13 December 2023

Suspected sockpuppets

[44] Same behavior as User:47.21.192.218 that Bbb23 blocked earlier today. Noah, AA Talk 22:10, 13 December 2023 (UTC) reply

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

16 December 2023

Suspected sockpuppets

Only contribution is to reinstate edit from a blocked IP sock, similar attempt to justify his reversion to other socks, and dubiously accusing others of assuming bad faith. Also request a global block, user is known to engage in cross-wiki harassment. ChrisWx 🌀 ( talk - contribs) 21:43, 16 December 2023 (UTC) reply

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

17 December 2023

Suspected sockpuppets

Obvious duck: See this attack against me. Was previously blocked as Andrew5 a few days ago, so needs longer block and global block. ChrisWx 🌀 ( talk - contribs) 15:41, 17 December 2023 (UTC) reply

Added another IP which reinstated a blocked sock's edit on Hurricane Isaias ( diff) and has also previously edited MLB-related pages, the usual Andrew5 targets. Also noting that the range 71.125.32.0/19 has been previously blocked for hosting Andrew5 socks. ChrisWx 🌀 ( talk - contribs) 21:58, 17 December 2023 (UTC) reply
Third IP added, cross-wiki harassment, sent harassing message on Wiktionary. ChrisWx 🌀 ( talk - contribs) 00:20, 18 December 2023 (UTC) reply

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

24 December 2023

Suspected sockpuppets

Duplicate edit on Tornado outbreak of December 10–11, 2021 ( [45]) to previous Andrew5 socks ( 69.118.238.21 & 47.23.40.14) The Weather Event Writer ( Talk Page) 18:50, 24 December 2023 (UTC) reply

Added 157.130.20.198 due to this duplicate edit. The Weather Event Writer ( Talk Page) 19:32, 24 December 2023 (UTC) reply
Added 204.150.3.195 due to yet a third edit on that article, duplicating the text in a now edit-war style fashion and somehow asking me to not file yet another SPI (Nice confirmation LOL!). Noting that 157.130.20.198 is blocked for vandalism at this time as well. The Weather Event Writer ( Talk Page) 20:08, 24 December 2023 (UTC) reply

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

27 December 2023

Suspected sockpuppets

Fairly new account with a similar editing pattern to Andrew5’s basic behavior: Wikipedia:Long-term abuse/Andrew5. A quick check can help verify if they are a true new unique account or Andrew5. The Weather Event Writer ( Talk Page) 03:04, 27 December 2023 (UTC) reply

Reply to @ Blablubbs: — These two edits on Hurricane Dorian add small, trivial-style facts to the article. The first edit actually mentions an MLB team being cancelled (Andrew5 often edits sports articles) (similar to this edit by a blocked sock and the 2nd edit was a trivial fact about a National Park being closed. That park being closed (trivial fact) is very similar to this edit & this edit & this edit by three previous blocked Andrew5 accounts. If I did a deep search through the list of Andrew5 IPs, I could probably link others do him. I forget which IP, but one of the Andrew5 IPs went through and used Accuweather a bunch in the past for snow/rain amounts, similar to this edit. It may be two editors, but the editing pattern seems oddly similar to Andrew5. Also the 3 Andrew5 IPs linked in the report on December 24th oddly all edited on December 24th and this account edited Dec 23/25th. We know Andrew5 didn’t take the Holiday off as they impersonated ChessEric twice on Meta-Wikimedia over the last 3 days. I want to assume good faith completely, but a check to verify if it is Andrew5 or a unique editor would be useful as the pattern seems to basically match the LTA to the letter (excluding personal attacks, which haven’t been on EN-Wiki for a while). The Weather Event Writer ( Talk Page) 01:51, 28 December 2023 (UTC) reply

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

28 December 2023

Suspected sockpuppets

Began their edits today reverting several edits by Yamla, who has just started rollbacks after blocking the previous confirmed Andrew5 sock CrossBayFan. They were previously blocked back on December 16, 2023. For sure WP:DUCK Andrew5 IP address. The Weather Event Writer ( Talk Page) 16:00, 28 December 2023 (UTC) reply

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

29 December 2023

Suspected sockpuppets

Every edit they made was to re-revert rollbacks from Andrew5 socks blocked yesterday by Yamla. Note, they are blocked for 1 week after making a death threat. This is a confirmed sock, block for 2+ years. The Weather Event Writer ( Talk Page) 16:35, 29 December 2023 (UTC) reply

Added 24.193.72.181. Re-reverting Andrew5 rollbacks as first edits today. Obvious WP:DUCK socks. The Weather Event Writer ( Talk Page) 16:43, 29 December 2023 (UTC) reply

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

29 December 2023

Suspected sockpuppets

Only edits as of this report is to attempt, once again, to roll-back edits from previous SOCKS. The Weather Event Writer ( Talk Page) 20:08, 29 December 2023 (UTC) reply

72.80.167.6 added as they went right back to edit-warring on the Andrew5 roll-backs. The Weather Event Writer ( Talk Page) 20:59, 29 December 2023 (UTC) reply

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

02 January 2024

Suspected sockpuppets

Editing sports-related articles and restoring sock edits where they were previously reverted. Also used edit summaries containing personal attacks, before engaging in page-move vandalism on an article where they were reverted, and attacking people who have been working against their sockpuppetry. Account is already blocked/g-locked, but I am requesting a CheckUser to see if there are any more sleepers waiting to gain autoconfirmed like this one. ChrisWx 🌀 ( talk - contribs) 19:25, 2 January 2024 (UTC) reply

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

19 January 2024

Suspected sockpuppets

A brand new account that started editing Draft:January 10-13, 2024 North American storm complex on January 19. On January 18, another new account ( JuneFan2939 was globally locked for being this sock master. 2nd edit ever from WinterStormFan was on the draft and first was on the parent winter storm article. SPI needed to check.

SEPARATE REPORT (NO SPI): Heavy WP:DUCK evidence on 152.179.91.86, who also edited the draft and parent winter storm. They stopped editing on January 15 and JuneFan2939 edited on January 16 on the draft. The IP created the draft and the only other 2 editors to it are JuneFan2939 and WinterStormFan. Can a 2nd administrator (Not checkuser) review the IP on DUCK evidence? The Weather Event Writer ( Talk Page) 23:38, 19 January 2024 (UTC) reply

Comments by other users

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

There is a reason I knew about the draft : Talk:2023-24 North American winter. Also, while I am not JuneFan2939, I doubt that he is related to CreamFan12. CreamFan12 was a vandal who harassed multiple users on Meta Wiki, and does not even exist on enwiki. While JuneFan2939 does exist on meta, they made no edits there and instead made constructive contributions to enwiki. This just seems to be the case of two irrelevant users connecting through a shared IP address. WinterStormFan ( talk) 18:40, 20 January 2024 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

03 February 2024

Suspected sockpuppets

Looks like Andrew has become a Swiftie to avoid detection. A public IP in New York that has previously edited weather articles (similar to Andrew5's previous IP socks) started inexplicably editing The Eras Tour and arguing that a section is a content fork. Then SwiftFan2024 comes and makes the same argument that the IP made. Not requesting CU on the IP for obvious reasons. wizzito | say hello! 03:23, 3 February 2024 (UTC) reply

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

17 February 2024

Suspected sockpuppets

Suspicious new IP (208.253.89.50) that started editing winter weather articles today (just like previous Andrew5 accounts). One of their first edits was adding trivial fact about NPS closing stuff, similar to a previous sock edit. They also did a second trivial addition minutes later. That is making me suspect WP:DUCK. Not to mention that second trivial addition was on January 13–16, 2024 North American winter storm, which was (basically) Andrew5's article with JuneFan2939 and WinterStormFan (recently blocked Andrew5 socks) having about 40% authorship of the article. This account seems to match WP:LTA/Andrew5 to a T. Also, they basically "DUCK confirmed" to be a new IP when editing Talk:June 2021 North American storm complex#Merge, by responding to a merge discussion started by another IP (108.58.71.234) a couple of days ago which also coincidentally is a brand-new editor with only a few edits. DUCK senses tell me this is Andrew5. The Weather Event Writer ( Talk Page) 23:44, 17 February 2024 (UTC) reply

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

18 February 2024

Suspected sockpuppets

[46] [47] - First two edits were to rollback deleted SOCK edits actually on this SPI talk page. CU requested since this is an account and not an IP. The Weather Event Writer ( Talk Page) 23:27, 18 February 2024 (UTC) reply

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

Chastick293 is confirmed to June10393 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki) and some logged-out shenanigans (no comment on the IPs previously mentioned). The technical evidence stretches further still. It all looks very likely to be Andrew5. -- zzuuzz (talk) 00:04, 19 February 2024 (UTC) reply

23 February 2024

Suspected sockpuppets

Restored deleted content added by previous IP sock that was blocked. Account only has 1 edit and was created today. WP:DUCK me thinks? -- MarioProtIV ( talk/ contribs) 15:35, 23 February 2024 (UTC) reply


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

29 March 2024

Suspected sockpuppets

(69.123.50.215) There second edit today (1 minute after their first edit today) was to complete a merge, which Andrew5 was confirmed (via blocked-sock 208.253.89.50) to have participated in along with a possible 2nd DUCK account. Their edit summary commented about that talk page discussion, where only 2 actual users commented + 2 Andrew5 comments. 69.123.50.215 is also working on Draft:December 2023 nor'easter, which is a common theme for Andrew5 socks — Being aware of draft-space weather articles. Seems very DUCKY here, given Andrew5 having confirmed knowledge of that merge discussion and then an unregistered user actually merging that discussion after only 4 registered users (2 commenters, the admin closer, and myself) seemingly having knowledge of said merge discussion…Also the 2nd unregistered user was suspected by myself along with the admin to have maybe been Andrew5, who coincidentally opened that merge discussion. I.e. based on DUCK evidence: Andrew5 wanted to merge the article, commented in it, had others agree, and finally today actually merge that article via a new IP address based on a talk page discussion which had 49 views in the last month. The Weather Event Writer ( Talk Page) 17:27, 29 March 2024 (UTC) The Weather Event Writer ( Talk Page) 17:27, 29 March 2024 (UTC) reply

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

30 March 2024

Suspected sockpuppets

Their first edit since 2007 was to reinstate a SOCK reversion edit saying “The sock is right though”. DUCK block needed on Andrew5 sock here. The Weather Event Writer ( Talk Page) 13:47, 30 March 2024 (UTC) reply

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

31 March 2024

Suspected sockpuppets

Their first edit since January 5 was to yet again revert a SOCK reversion edit for that merge discussion. Easy DUCK account of Andrew5. The account also edit warred for it with Fantastic Mr. Fox. The account was also previously blocked for 1 month for ban evasion. Given previous block and edit warring behavior, requesting the 2-year block which previous Andrew5 IPs have received. The Weather Event Writer ( Talk Page) 15:26, 31 March 2024 (UTC) The Weather Event Writer ( Talk Page) 15:26, 31 March 2024 (UTC) reply

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

06 April 2024

Suspected sockpuppets

DUCKY chances seem high that this is Andrew5. Their first edit on Wikipedia was in an AFD, which is currently nominated for a TNT due to SOCK copyright violations. A confirmed SOCK from Lokicat3345 did edit the article, however, several IP users have also edited the article, including one of the large copyright violations. Andrew5 and/or Lokicat3345 are often is aware of non-mainspace things (like AfDs or drafts). My senses also went up as that AFD comment (their first edit) stated “We are becoming way too lax in giving individual tornadoes article (emphasis mine), followed by them listed two articles (a GA and a GAN) which I created. A brand-new editor should not be that familiar with things, let alone trying to AfD an active GAN two minutes later. This is definitely a SOCK of one of the two weather-sock masters, I just don’t know exactly which. Andrew5 is my gut due to edits like this mentioning policy and things like a behind-the-scenes effort of WikiProject Weather to reassess GA articles. No new editor should even be aware of that process, but Andrew5 100% would and DUCK evidence from previous SOCKs back that idea up. The Weather Event Writer ( Talk Page) 14:29, 6 April 2024 (UTC) reply

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

08 April 2024

Suspected sockpuppets

100.12.36.99's first edits in the last two years was to nominate Elizabeth Leitman for deletion. Majority of their edits in 2022 were weather-related plus an edit on Long Island City (NYC, where Andrew5 is located). Coincidentally, I started this article and Andrew5's latest IPs went on a shpeal about several articles (all of which I started) needing to be deleted. Both this AfD request and the one tried for 2022 Pembroke–Black Creek tornado were posted on Wikipedia talk:Articles for deletion coincidentally a day apart. 174.216.209.32's only edit was to PROD that article. In fact, 174.216.209.32's PROD is the exact same and idential AfD reasoning that 100.12.36.99 put out. Also coincidentally, both of these IPs started edited mere hours after Andrew5 was blocked on 3 IPs. I feel confident on a DUCK report for 100.12.36.99, however, 174.216.209.32 was listed more for future reference of being suspected Andrew5. The Weather Event Writer ( Talk Page) 23:21, 8 April 2024 (UTC) The Weather Event Writer ( Talk Page) 23:21, 8 April 2024 (UTC) reply

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

23 April 2024

Suspected sockpuppets

First edit since 2011 started with “As per usual, WeatherWriter is endlessly yapping” and on Wikipedia:Articles for deletion/2023 Little Rock tornado, where Andrew5 was already blocked once this month. Easy DUCK confirmation. The Weather Event Writer ( Talk Page) 14:57, 23 April 2024 (UTC) reply

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

23 April 2024

Suspected sockpuppets

First edit in 3 years was to revert a strikethrough of a comment by a blocked Andrew5 IP (the other one reported today). Easy DUCK ban. The Weather Event Writer ( Talk Page) 23:07, 23 April 2024 (UTC) reply

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

26 April 2024

Suspected sockpuppets

Only edit in 2024 was to restore Andrew5 SOCK content. DUCK block requested on the IP. User:Colorado is not New York WeatherWriter was added for CU review. The account is currently perm blocked due to username violation, however, this is almost certainly Andrew5 due to what the username is. The Weather Event Writer ( Talk Page) 03:02, 26 April 2024 (UTC) reply

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

11 May 2024

Suspected sockpuppets

Immediately resumed prior behavior for which they had been blocked. Noah, BSBA Talk 15:39, 11 May 2024 (UTC) reply

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

11 May 2024

Suspected sockpuppets

For the 71... IP, it has added trivial content about airport/road closures into recent tornado outbreak/winter storm articles ( here and here), has edited multiple sports-related articles since December 2023, and edited Andrew5's LTA page shortly after attacks took place on Meta, linking to them here. The IP has also edited Wikipedia:Long-term abuse/Samlaptop85213, an LTA page one of his socks created ( here). It has been intermittently active for multiple months in the same topic areas of sports and weather. For the 69... IP, it has edited 2 recent tornado outbreak articles today, and edited several sports-related articles on teams and players in football. His linking to certain policies while making edits, like this one, as well as the particular topics the IP has edited of sports and weather since July 2023 also leads me to believe this is an Andrew5 sock. ChrisWx 🌀 ( talk - contribs) 22:52, 11 May 2024 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • I added 96.57.52.66 for future WP:DUCK reference. Back in March 2024, 71.190.208.91 made reference to a previous WP Weather debate ( Wikipedia:Articles for deletion/List of United States tornadoes in May 2008). 71.190 did not comment in that discussion, however 96.57 did. 96.57 has also coincidentally not edited since January 2024, however, their last edits was on 2023–24 North American winter, which 71.190 edits. Andrew5 is also familiar with winter-storm articles. Also coincidentally, 96.57 and 71.190 never edited on the same day, but seem to edit the same articles (late-December 2023 to mid-January 2024), specifically a lot on that winter article. 96.57 shouldn't be blocked as they are inactive, but noting that DUCK connection for future references.
Also noting 71.190 is picture-perfect Andrew5 sock. Within their last 50 edits, we have sport edits, winter storm edits, hurricane edits, tornado edits, and most importantly, even an edit on WP:LTA/A5, which funny enough is LTA DUCK evidence as Andrew5 is familiar with that specific behind-the-scenes page as well as this SPI page. The Weather Event Writer ( Talk Page) 23:07, 11 May 2024 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

30 May 2024

Suspected sockpuppets

Edit history would suggest this is a WP:DUCK of Andrew5. Between 2023-24, they have made less than 50 edits, consisting of sports (baseball) and weather edits, even on the same day (20 May 2023). This is exactly the lookout on WP:LTA/A5. Coincidentally (DUCK-coincidence), their first edit in several months happen to also be telling others to discount my !vote in a requested move discussion. This is also common Andrew5 behavior, with either personal attacks against other weather editors (plus a few admins) or inserting themselves in discussions in an attempt to say several long-term editors are stupid/irrelevent. Even if they have not edited recently when this SPI is reviewed, if the reviewing administrator feels this is Andrew5 DUCK evidence, I would still appreciate a block or some agreement statement at least, given they are involved in an ongoing RM discussion. The Weather Event Writer ( Talk Page) 09:18, 30 May 2024 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
  • So um what exactly did Andrew5 do wrong? Those edits look fine, not disruptive, quite helpful and productive actually. Is it just because he’s “socking?” Well, SchroCat blatantly engaged in abusive sockpuppetry but is still allowed to edit. In fact he never had to serve the sanctions that the community decided he deserved. Why doesn’t he get blocked?? Maybe it’s time to realize that Andrew5 is actually an enthusiastic contributor to wikipedia… or else block SchroCat. Can’t be treating certain people differently. Defjotme ( talk) 12:21, 7 June 2024 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

19 June 2024

Suspected sockpuppets

Second IP protested and re-inserted sports-related material that was deemed trivial on June 2024 South Florida floods, two areas Andrew is notorious in. After the first removal, the first IP reverted it again, and then when taken to talk page, the first IP proceeded to argue for its inclusion by mentioning the team names and score. Reeks of WP:DUCK here. Additionally, both added trivial information to Draft:Effects of Hurricane Ian in Florida. -- MarioProtIV ( talk/ contribs) 16:33, 19 June 2024 (UTC) reply

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

Retrieved from " https://en.wikipedia.org/?title=Wikipedia:Sockpuppet_investigations/Andrew5/Archive&oldid=1234197625"

Videos

Youtube | Vimeo | Bing

Websites

Google | Yahoo | Bing

Encyclopedia

Google | Yahoo | Bing

Facebook




Top Of Page

Home • Search • Translate

© CSE