Reading List
The most recent articles from a list of feeds I subscribe to.
Contrary to Rumors, Apple Will Continue Broadcasting ‘Friday Night Baseball’
Anthony Castrovince, reporting for MLB.com on the new broadcast rights agreement that will cover the next three seasons of baseball:
Sunday Night Baseball will shift from ESPN, where it aired since 1990, to NBCUniversal, which also secured the rights to Sunday Leadoff and the Wild Card Series in the postseason for NBC and Peacock.
Netflix will now air the T-Mobile Home Run Derby, an Opening Night exclusive and special event games set to include the 2026 MLB at Field of Dreams Game and the World Baseball Classic in Japan.
And ESPN will receive a national midweek game package throughout the season while also acquiring the rights to sell MLB.TV, the league’s out-of-market streaming service that set a record with 19.4 billion minutes watched in 2025. [...]
FOX/FS1 will continue to be the home of the All-Star Game and regular season games, as well as the World Series, League Championship Series, and Division Series presented by Booking.com. TBS will continue to house LCS and Division Series telecasts, plus regular season games on Tuesday nights. Apple TV will continue to stream “Friday Night Baseball” doubleheaders throughout the regular season.
Back in August, Kendall Baker of Yahoo Sports reported:
- Apple is fully out. RIP Friday Night Baseball
- NBC/Peacock is in, for Friday and Sunday exclusive and Wild Card
- MLB TV being sold to ESPN (for a boatload of $$$)
- Netflix gets HR Derby
He batted .750 on that tweet.
Cloudflare’s Uptime and Scale
Miguel Arroz, on Mastodon:
Unpopular opinion, apparently: companies like Cloudflare and Amazon provide very high quality services people and enterprises actually need, with a level of uptime and security vastly superior to what most of their customers would achieve on their own or using traditional providers. Their downtimes being so visible is a consequence of their success.
A few readers have (very politely!) asked me whether yesterday’s outage (which made DF unreachable for, I think, about 90 minutes) made me rethink relying on a centralized provider like Cloudflare. My answer is no.
Until I started using Cloudflare in 2018, Daring Fireball relied on no upstream service. I paid for a server from a web hosting provider (those providers changed a few times over the years), and when you, a reader, requested a page on this site, your browser communicated directly with my server via HTTP requests and my server responded directly back. The basic architecture of the World Wide Web is beautifully simple, and I embraced that simplicity with the way I hosted and served Daring Fireball.
But the move away from HTTP to HTTPS added a lot of complexity. That complexity is probably worth it, overall, but it came at the price of simplicity. I originally made the switch to using Cloudflare as a caching front-end for Daring Fireball as a solution to an SSL-related slowdown that affected only some visitors in 2018. But I’d started using Cloudflare to handle my DNS the year before.
Daring Fireball has always been a fast website and has always had very good uptime. That’s not because the back end is cleverly architected, but rather because it’s so simply architected. But DF’s overall uptime and the frequency of any sort of performance problems went from good to great when I started relying on Cloudflare as a proxy. Also, in recent years, bot traffic has exploded. (Thanks, AI.) I’m pretty sure my server could handle those bursts of traffic on its own, but I sleep better not having to worry about it, because Cloudflare handles mind-boggling amounts of traffic.