Texas
Back in the MLB All-Star Game, Texas Rangers reliever Kirby Yates made this one count
ARLINGTON — Kirby Yates’ children were too young to remember their dad’s first trip to the All-Star Game. His kids — Oaklee and Kove — were 2 and 1 when the Texas Rangers’ closer was named to the National League roster five seasons ago as a member of the San Diego Padres.
In hindsight? It worked out fine. They’ll remember the one that mattered more.
Yates, who did not pitch in that 2019 All-Star Game in Cleveland, made his midsummer classic debut Tuesday night at Globe Life Field. He made it count, too.
Kirby Yates’ only other All-Star appearance was in 2019. He didn’t get to pitch in the game.
Yates made the most of the opportunity this time around in front of the home crowd. 🔥🔥🔥
(Via @Rangers)pic.twitter.com/l63tNlTbgv
— SportsDay Rangers (@dmn_rangers) July 17, 2024
The 37-year-old right-hander — who’s in the midst of a career revival after a number of injuries stalled it — pitched a perfect eighth inning and struck out two batters in the American League’s 5-3 win inside the Rangers’ home park.
He was one of three Rangers players who competed in Tuesday’s exhibition, joining second baseman Marcus Semien (a three-time All-Star) and shortstop Corey Seager (a five-time All-Star). Rangers manager Bruce Bochy and his assistants served as the AL’s coaching staff.
Yates struck out Washington shortstop C.J. Abrams on three pitches, including an 87.2 mph splitter that got the 23-year-old to whiff for strike three, and ran a 94.2 mph fastball past San Francisco outfielder Heliot Ramos in the next at-bat for his second strikeout. Los Angeles catcher Will Smith bounced out to third base on three pitches to end the inning.
“You’re always kind of going in there trying to do an immaculate inning, and I was off to a good start then messed that up,” said Yates, who walked off the field to a standing ovation from the home crowd. “You just don’t want to suck, let’s put it that way.”
He didn’t, and he hasn’t this season. Yates posted a 1.05 ERA, 46 strikeouts and went 16 for 16 in save opportunities for the Rangers in the first half. The Lihue, Hawaii native estimated that somewhere between 20 to 30 family members made the trip to Texas to watch him throw.
Their journey matched Yates’ own. He led the NL with 41 saves and had a 1.19 ERA in 2019, but an elbow injury derailed his 2020 season and he underwent Tommy John surgery that forced him to miss the entire 2021 season. He pitched for the Atlanta Braves last year but never quite felt like himself.
He became an All-Star again this season. The whole family got in on the fun this time.
“It just didn’t involve me, right?” Yates said. “It involved my wife, it involved my kids. We made a decision to leave our home, go somewhere else to rehab, take all the necessary steps, put our kids in a school in a place we weren’t familiar with. Did all these things that we thought were right to help my career get back to where I needed to go, and it’s just rewarding and all of that.
“It wasn’t just me, there was a village that was behind this.”
Yates, like many, grew up a Ken Griffey Jr. fan. He and his kids took a photo with Griffey on Monday night during the Home Run Derby. Both accompanied Yates and his wife, Ashlee, down the red carpet prior to Tuesday’s game.
“I know they were really nervous walking down the red carpet,” Yates said. “But I think once they got going, they kind of relaxed a little bit. My daughter loved it. It’s just neat to be able to spend it with them, because I hope it’s something they remember, too.”
Seager — who replaced Baltimore’s Gunnar Henderson at shortstop prior to the fifth inning — nearly gave the AL a lead in the ballpark in which he’s hit so many memorable home runs. In a six-pitch at-bat vs. Cincinnati fireballer Hunter Greene, Seager drilled a slider just outside of the right field foul pole, then sent a 96.3 mph fastball deep into center field immediately after. Los Angeles Dodgers center fielder Teoscar Hernández chased it down at the warning track.
The 102.9 mph, 402-foot flyout would have been a home run in 17 ballparks, according to Baseball Savant. Just not at Globe Life Field, where the Rangers’ home run song (the theme from The Natural) briefly played after Hernández’s grab.
“Did it really?” Seager asked. “Oh no, that’s bad mojo right there.”
And, on the topic of possibly weird mojo, Seager did not bat directly behind his double-play partner Semien as he usually does for the Rangers. Semien — Texas’ leadoff hitter — started at second base and hit ninth for the AL. He went 1 for 2 with a single and a run scored off of San Francisco Giants right-hander Logan Webb as part of a three-run third inning.
“It was weird not playing up the middle with him, too,” Semien said. “Gunnar is a big shortstop, similar build [to Seager]. He made a nice play out there. Corey and I, our goal is to be playing up the middle in these things.”
Semien, a finalist to start at second base, replaced Houston’s Jose Altuve on the roster when the latter pulled out to rest a sore hand that was hit by a pitch on July 5. Seager had a significantly shorter runway. He learned at around 6:45 p.m. Sunday that he’d been called upon to replace Minnesota shortstop Carlos Correa (plantar fasciitis) on the roster.
He and his wife, Madisyn, even had to cancel vacation plans.
“I don’t want to say we were panicked, but we were a little panicked,” Seager said. “[The red carpet] is intimidating if you don’t have time to plan for it, but she looked amazing and we had a great time.”
So did the eldest of the trio.
“It’s all surreal, I won’t ever forget this,” Yates said. “The fans were awesome, it was great, and I’m very appreciative.”
Twitter: @McFarland_Shawn
Find more Rangers coverage from The Dallas Morning News here.
Click or tap here to sign up for our Rangers newsletter.
Texas
NTSB Confirms Texas Tesla Had 100% Floored Accelerator Pedal During Fatal Crash
In an incident that was horrific beyond words, late last month, a stunned family watched in horror as a car plowed into the Katy, Texas home of a 76-year-old mother and grandmother, killing her. The driver has been charged with manslaughter.
In the aftermath of the crash, it emerged that the car in question was a Tesla, and that the driver was making use of full self-driving mode (FSD) around the time the crash occurred. The victim’s family has named Tesla and the driver as defendants in a lawsuit. But per Electrek, Tesla was able to view crash data very quickly after the incident, and the head of AI at the company, Ashok Elluswamy, said the driver “manually overrode self-driving by pressing the accelerator all the way to 100% of the accel pedal in this residential area.”
In the days after the crash, Tesla fans took issue with coverage that characterized the car as in FSD when the crash occurred. CEO Elon Musk seemed to agree, replying to a post, “Yes, this makes no sense. FSD drives slowly through neighborhood streets and this was a high speed crash!”
But Musk seems to be assuming bad faith, as if coverage implied FSD had suddenly shifted into, perhaps, some kind of previously unannounced homicidal maniac mode and attacked a house. If anyone was saying this is what happened, they should apologize. It’s clearly not what happened.
And on Wednesday, the National Transportation Safety Board (NTSB) largely confirmed Tesla’s version of events. Their report reads, in part:
“Electronic data recovered from the vehicle indicated that before the crash, the driver manually overrode FSD (Supervised) by pressing the accelerator pedal to 100%, and the vehicle’s speed was greater than 70 mph when the crash occurred.”
But cooler heads had noted weeks earlier that, like with good old fashioned cruise control, accelerating doesn’t boot you from FSD. The car takes the input, and stays in FSD. The question isn’t one of mechanics and technology, but one of philosophy: if FSD is meant to be “driving” when someone jams on the accelerator in a residential area, FSD may not be the “driver” in one important sense, but the car was still in FSD mode.
Because as much as Tesla would probably like FSD to be a total non-factor in the incident, that may not be the case either.
ABC News noted that, according to court documents, the driver claimed he “passed out” with the car in FSD on the highway, and that’s the last thing he remembers before the crash. He says he wasn’t sick, and medical records show no seizures, cardiac episodes, drugs, or alcohol.
A local Fox affiliate says records show the car was making deliveries for DoorDash while in FSD in the “hours and minutes leading up to the crash.” While in a neighborhood, it apparently signaled it was going to turn left onto one street, but instead the pedal went to the metal. This took the Tesla onto the victim’s cul-de-sac instead, and put it on its fateful collision course with her house.
To make matters weirder, other court records now show, per Electrek, that the driver had Googled the terms, “Tesla fsd not aggressive enough 2026,” “FSD is not aggressive enough for city driving,” and “Tesla fsd too timid.” That’s the kind of thing you Google when you’re looking for a Reddit post from someone sharing your consumer gripe.
In any case, the odds aren’t good that the driver wanted this to happen, nor that Tesla programmed its cars with evil intent. But FSD was being used around the time of this unusual fatal incident, and the public deserves to know more. Fortunately, a lot more will come out as the lawsuit progresses.
Texas
Texas AG secures 23andMe bankruptcy settlement after 2023 data breach
AUSTIN – Texas Attorney General Ken Paxton said Wednesday he has secured a settlement of bankruptcy claims against genetic testing company 23andMe stemming from a 2023 data breach that exposed personal information, including some genetic ancestry data, of 6.9 million customers worldwide.
Paxton’s office said the settlement includes $150 million for a multistate coalition of 42 states. But because of limited funds in 23andMe’s bankruptcy estate and competing claims, the states’ recovery will be $18 million paid immediately, with Texas receiving $1,266,860.
23andMe disclosed in October 2023 that attackers had accessed accounts affecting 6.9 million consumers. Some of the information was later posted for sale on the dark web, according to Paxton’s office, which said the company learned of the breach months after the data became publicly available. The office said 23andMe initially denied a breach and later blamed consumers’ account settings and password practices.
Paxton joined a multistate investigation that concluded 23andMe used unreasonable security practices and failed to implement adequate safeguards against hacking, the office said.
23andMe filed for bankruptcy protection in March 2025. Paxton’s office said the settlement incorporates privacy and cybersecurity requirements, including enhanced security standards, comprehensive risk assessments and creation of an independent advisory board, along with enforcement of state privacy laws and continued consumer data deletion rights.
“Companies that collect and profit from Texans’ most personal information have a legal duty to protect it,” Paxton said in a statement.
The company also agreed to a $46.75 million class-action settlement in the bankruptcy case for affected U.S. consumers who submitted claims by Feb. 17, 2026, Paxton’s office said.
Copyright 2026 by KPRC Click2Houston – All rights reserved.
Texas
Texas Makes Announcement Featuring Arch Manning
-
Virginia5 minutes agoVirginia Tech HC James Franklin Gives High Praise For Clemson’s Dabo Swinney
-
Washington11 minutes agoWill air quality be even worse in Washington DC on Friday?
-
Wisconsin17 minutes agoLIVE UPDATES: Wisconsin air quality, wildfire smoke blankets region
-
West Virginia23 minutes agoRepair work on busiest bridge in West Virginia to happen in phases to “minimize disruptions”
-
Wyoming29 minutes ago
Wyoming Rodeo Stars Set for National High School Finals
-
Crypto35 minutes agoNew law protects consumers from cryptocurrency kiosk/ATM fraud | Maui Now
-
Fitness47 minutes ago‘This works’: Fitness icon Suzy Jalowsky, 60, shares the simple exercise formula she swears by
-
Movie Reviews59 minutes agoMovie Review: “The Odyssey”
