Central chokepoints keep breaking things for builders
Several threads show how one provider's decision becomes everyone's outage. Docker pull fails in Spain because Cloudflare gets blocked during La Liga football matches (47738883), with R2 blocked wholesale and Docker Hub as collateral. AWS showed customers bills like $286 million on hobby accounts in an "Inaccurate Estimated Billing Data" incident, with one total quoted at $1.7 billion (48945241). Recipes are moving from Maven Central to the Code Genome Project, behind a private repository that requires registering for an access token (50104783), and commenters called Maven Central's monetization strategy bizarre. eBay is restricting radio equipment listings while exempting gear that operates only on ham bands (50122034).
Older threads in the feed (Stripe nuking a business, Google Cloud suspending production, Cloudflare blocking Pale Moon, Slack closing IRC gateways) read as the same story from earlier years.
The through-line: your product sits on top of several companies' policies, billing systems and legal fights, and any of them can change without asking you. Open, boring, replaceable layers are slowly being swapped for gated ones.
So what?
Map your single points of failure: registry, CDN, cloud, payments. Mirror your critical packages and container images, set hard billing alarms, and have a tested way to move off any one vendor.
Read these
Tell HN: Docker pull fails in Spain due to football Cloudflare block
AWS: Inaccurate Estimated Billing Data – $1.7 billion
Recipes Are Moving from Maven Central to the Code Genome Project
eBay Restricts Listings of Radio Equipment, but Exempts Ham-Band-Only Gear