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 mired in a 4-game losing streak. It’s unfortunate. Of course, last night the bullpen pitched great with Brad Lord and Zak Kent — and it was the offense that didn’t do their job as they scored just 1-run en route to a 4-1 loss.
The Washington Nationals were one pitch from taking the first three games in the series then a 2-out home run with two strikes turned into another gut-punch Nats loss. This was like a replay of Tuesday. Baseball can be cruel. Even President of Baseball Operations, Paul Toboni, publicly said that he was “freaking pissed off” after Tuesday’s loss. Wonder how he felt after last night?
The Washington Nationals can tell you that losing isn’t fun. Especially when you were one pitch away from a key win on the season. The mark of a good team is shaking off a tough loss and beating the team that just embarrassed you.
The Washington Nationals got going in the right direction last night with a solid 4-1 win over the Phillies. Of course the score should have been much larger if the Nats weren’t jobbed by umpire Jeremie Rehak who per Umpire Scorecard cost the Nats an additional 2.42 runs.
The Washington Nationals have a scheduled four game series with the Phillies as they battle for Wild Card spots. The Nats have their best statistical pitcher in terms of wins on the mound with Foster Griffin.
We will see if the weather cooperates for this one. Expect a delayed start, and go from there.
The Washington Nationals wrap-up their Father’s Day weekend in Tampa with a chance to win another series. The players, coaches, front office and staff, along with their fathers who made the trip to Tampa, will board the team’s Delta charter jet for a flight back to Washington, DC after this game.
The Washington Nationals seemed to lose focus after Miles Mikolas lost the lead on Friday. The Nats never scored again and have now lost two games in a row while only scoring two runs per game from the most potent offense in baseball.
The Washington Nationals hit their high-mark of the season last night at 4-games over .500. The Nats also tied their season’s best 4-game winning streak in that game.
On July 6, 2019, the Nats beat the Kansas City Royals to get to 4-games over .500, and that was the last time the team had seen that exact point above the .500 mark before this. In winning last night, the Nationals clinched the series win against the Kansas City Royals. This afternoon marks the season finale against Kansas City, and the Nats can get to 5-games over .500 like they did on July 7, 2019 against the Royals.
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.