Click to Read an Important Member Update Regarding Our Comment System
We recently upgraded our comment system to improve reliability, performance, and long-term control, and we’re currently running both systems during the transition. This shift moves us away from an external service to a system we run and control directly—meaning we own the content and can continue improving it over time. We’ve also reduced the comment refresh delay from about 30 seconds to 10 seconds, making it much closer to real-time.
We understand there have been frustrations and increased feedback, and we’re actively working to improve things. What we ask is simple: use the system and give it a fair shot. If you run into issues, please submit them through the support form so we can track and fix them properly. Repeated complaints without details don’t help us solve problems—we appreciate your patience as we continue refining the experience.
If you’d like a full side-by-side comparison of the platforms and the reasons behind this decision, please refer to the chart below. This change is being made with the long-term benefit of the entire community in mind.
Built by Nationals Fans. Powered by the Conversation.
The Washington Nationals are set to play the second game of this doubleheader (subject to the inclement weather) with MacKenzie Gore on the mound. The Nats have dropped the first two games of this four game series.
Well, for those, myself included, who were hoping to see the Nationals’ offense take advantage of a bullpen game in the first of two today, we were sorely disappointed. The Nats allowed Jose Suarez, who likely wasn’t supposed to go more than 4-5 innings at most, to cover seven innings of two-run ball in just his fourth big league appearance on the season. What’s worse, he hadn’t gone more than 3.1 innings yet this season. In the longest outing he’s had since 2022, the southpaw not only completed seven innings, but racked up nine strikeouts in the process against a Nationals lineup that’s just been a total disaster against lefties this season.
The Washington Nationals have a scheduled doubleheader for today just as a storm is moving up the east coast to wreak havoc in the Mid-Atlantic region. If the games get played, it is Jake Irvin on the mound for the first game followed by MacKenzie Gore for the nightcap.
For three innings of last night’s contest it looked like Mitchell Parker had turned a corner and was en route to back-to-back good outings after his 7.2 innings in Miami. Then, unfortunately, the other Mitchell Parker resurfaced. The Braves got to him for five additional runs in the next 2+ innings for a total of six runs, and the game was pretty much over from there, thanks in part to a bad night from most of the offense as well.
The Washington Nationals have the Atlanta Braves in for four games in three days. Tonight is another Mitchell Parker start. He had a 7-1 lead through 7.0 innings last week and was asked to pitch the 8th inning. That did not go well. So, we will see if Parker is the pitcher we saw for the first 7.0 inning last week or the 8th inning guy.
You must be a TalkNats Subscriber to access this content. Subscribers have access to exclusive content on the TalkNats website and can engage in discussions with other Nats fans. Click here to become a subscriber.
First two weeks are free and then you will be billed $3.99/month. Cancel anytime. Secure payments using Stripe.
If you are already a subscriber, simply log in using the form below.
The Washington Nationals were in a Saturday pitcher’s duel between the starting pitchers, and then the Nats got some hustle and clutch hitting from the combo of Dylan Crews and Robert Hassell III as they manufactured a run that broke the ice. And by the way, Crews broke up Bubba Chandler‘s perfect game in the 6th inning. But the Nats bullpen wasted Andrew Alvarez‘s 6-inning scoreless gem. The Nats took their 1-0 lead into the 8th inning and just couldn’t finish it off, and lost 5-1 after a bullpen implosion.
For humans, change can be the enemy. Change can be scary. Change can be viewed as something to be avoided, both big and small. In the 20 years of Washington Nationals baseball in DC, change is not something we’ve encountered when it comes to the voice we hear as we turn on our televisions to watch the team we love. Bob Carpenter was hired by the Nationals in 2006 to be the television voice of the team, a brand new team in our nation’s capital. No pressure! Bob took this job and ran with it — and on September 28, his final day on MASN, he will have 20 baseball years completed.
The Washington Nationals were down 3-runs early last night, and chipped away until they added 6-runs to take a 6-3 lead. The outfielders led the way in this one on offense and defense. Not only did Dylan Crews hit a 2-run homer to give the Nats a 4-3 lead, he also made a leaping catch at the wall and several other plays, and James Wood had 2-hits and the play-of-the-game by nailing the potential tying run at home in the 9th inning on a 93.1 mph dart to catcher Jorge Alfaro. This was definitely the game of the outfielders as Robert Hassell III added 2-hits and perfect defense.
The Washington Nationals should not have had a happy flight back to DC. While the road trip was successful, they had a chance to win the 4-game series in Miami, but instead split it. The Nats American Airlines flight AA 9721 landed at 1:30am at Dulles and as MASN’s Bob Carpenter said on-air, he expected a 3am arrival back to their pillows. The good news is everyone gets to sleep in today and will start arriving after 1:30pm at Nationals Park for their weekend series against the Pittsburgh Pirates.
We recently upgraded our comment system to improve reliability, performance, and long-term control, and we’re currently running both systems during the transition. This shift moves us away from an external service to a system we run and control directly—meaning we own the content and can continue improving it over time. We’ve also reduced the comment refresh delay from about 30 seconds to 10 seconds, making it much closer to real-time.
We understand there have been frustrations and increased feedback, and we’re actively working to improve things. What we ask is simple: use the system and give it a fair shot. If you run into issues, please submit them through the support form so we can track and fix them properly. Repeated complaints without details don’t help us solve problems—we appreciate your patience as we continue refining the experience.
If you’d like a full side-by-side comparison of the platforms and the reasons behind this decision, please refer to the chart below. This change is being made with the long-term benefit of the entire community in mind.