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 returned home last night after a quick west coast swing that finished with three games in Kansas City. A 3-and-3 road trip gets the Nationals back to face the two best teams in the NL East with the Phillies in for 4-games followed by a 3-game series against the Mets.
The Washington Nationals opened up a 5-0 lead in the first inning in this game this afternoon in Kansas City, only to see that lead go away very quickly. After the Royals tied it up in the eighth, my hopes of winning this one were pretty bleak, but the offense had one more rally in them, capped off by a Luis Garcia Jr. double followed with the game-winning single by Daylen Lile in the top of the ninth.
The Washington Nationals have put themselves in a salvage game situation as they wrap up this afternoon in Kansas City. Days like this show the importance of why you go for it aggressively as we did not see on Monday — because you don’t know what will happen in the rest of the series. Yes, you can’t play most regular season games like they are a postseason elimination games however the issue is manager Miguel Cairo shoved his starting pitcher with a 4-2 lead and with a rested bullpen went to his worst reliever after that.
The good vibes from wins on Saturday and Sunday in San Francisco were quickly erased in Kansas City. That is the ups and downs of baseball. Unfortunately for the Nats, it has been a season of 47 ups and 72 downs.
The Washington Nationals were in control last night until Miguel Cairo tried to push Cade Cavalli for more. That was such a Davey Martinez type of move that almost always backfired in more ways than one. Cavalli has shown that he just does not have the stamina to go deep in games. The 4-2 lead through 5.0 innings — should have been sufficient. Instead of pulling Cavalli at the first sign of trouble in the 6th inning, Cairo let Cavalli self-destruct then went to the team’s worst statistical reliever and brought in Jackson Rutledge who turned it from a tie game to a 2-run deficit. When will they learn?
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.
On this night, Cade Cavalli made it through five innings of two-run ball in Kansas City, then he was sent back out for the sixth. While I have no problem with that decision, after he walked the leadoff batter, it should’ve been a sign to Miguel Cairo that he could be at the end of his rope. That’s not what Cairo interpreted unfortunately, and the next batter, Salvador Perez, made the Nats pay by smashing a two-run homer out to left to tie the game. Four batters later against Jackson Rutledge, Kyle Isbel smacked a two-run shot of his own to give the Royals a 6-4 lead, and they wouldn’t look back from there.
The Washington Nationals looked as good as you can look on Saturday and Sunday in a polar opposite to how bad they looked on Thursday and Friday. What the Nats need to do is bottle up what they did against the Giants yesterday and future Hall-of-Famer, Justin Verlander, who they torched for five earnies in 5.0 innings.
The Nationals only have 14 series remaining this year with an even split between road/home series right now. And only this series in Kansas City and an early September series in Chicago against the Cubs are against teams not on the East coast.
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.
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 got a really good day from their pitching on Saturday to win 4-2. There was certainly a power surge for the Nationals, but they still are not piecing together singles and doubles to score more runs.
This game marks the final West coast game of the season for the Nationals as they will fly next to Kansas City with just 45 games remaining in the season. First things first, the Nats have a series win to get today against the Giants.
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.