Hi, everyone.
I’m Quinn Riley, and I’m excited to join TalkNats and bring coverage of the Nationals and the farm to TN.
Having a background with Boston sports, I covered the five major Boston teams for 17 months before moving on to RedSoxDigest.com in July of 2022. My most recent gig was to focus solely on the Red Sox. Covering five teams at once with limited help is often very taxing, so focusing on one team is a major plus.
I had been at RSD for the past nine months and have brought daily Red Sox coverage to the site. However, covering the Red Sox might be one of the more challenging things — there are roughly two dozen sites covering the team and a whole array of Sox podcasts as well, which make it one of the most saturated media environments.
So, with how competitive it is, it’s not exactly always the easiest to grow. When we had sort of begun to hit a wall in terms of growth, I began to search for different opportunities.
When I learned I could join TalkNats, it was sort of a no-brainer. Washington isn’t exactly the greatest team currently, but with a good young core, great prospects, and a site that has a phenomenal community and following, it was all that I needed for me to join the site.
And that leads us to where we are now.
I look to bring game recaps and both major and minor league coverage to TalkNats. In fact, we’ve even created a prospects-based account, @ProspectsTN, so you should go give that a follow. Geographically, I am located between Harrisburg, PA the home of the Nats Double-A affiliate and Wilmington, Delaware, the Nats High-A affiliate, and plan on attending games in person there and catching some Nats’ Triple-A and Class-A on the road at games near me. With that, I will concentrating on the affiliates and the Top Prospects as well as developing Nats’ stories.
And that’s that, as I’m eager to begin the next part of my writing career. Shoot me a follow @QuinnRileyTN on Twitter if you will, and let’s have some fun. Look forward to interacting with all of you Nats fans.
Cheers.




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.