Quick, Blame the DBAs!
Episode Summary
The walled garden wrecking ball is fueling up - where we think it strikes first. Plus, what was really behind the recent GitHub outage.Sponsored By:Coder QA: Take $1 a month off for the lifetime of your membership and contribute to our show directly. Promo Code: summerSupport Coder RadioLinks:💥 Gets Sats Quick and Easy with Strike — Strike is a lightning-powered app that lets you quickly and cheaply grab sats in over 100 countries. Easily integrates with Fountain.fm. Setup your Strike account, and you have one of the world's best ways to buy sats.📻 Boost with Fountain.FM — Boost from Fountain.FM's website and keep your current Podcast app. Or kick the tires on the Podcasting 2.0 revolution and try out Fountain.FM the app! 🚀Raspberry Pi 5 2GB Launches At $50 USD — Upton explained of the new Broadcom BCM2712 D0 stepping that it eliminates some dark silicon that goes unused by the Raspberry Pi boards but ultimately impacts the die space/pricing and is now eliminated with this new steppingEpic judge says he’ll ‘tear the barriers down’ on Google’s app store monopoly — udge James Donato will issue his final order on what Google gives — and Epic gets — in mere weeks.US Considers a Rare Antitrust Move: Breaking Up Google — This action would mark Washington's first attempt to break up a company for illegal monopolization since the failed bid to dismantle Microsoft two decades ago.GitHub rolls out AI-powered fixes for code vulnerabilities — Copilot Autofix, a new addition to the GitHub Advanced Security service, analyzes vulnerabilities in code and offers code suggestions to help developers fix them. GitHub rolls back database change after breaking itself — "We are experiencing interruptions in multiple public GitHub services," the source code silo said in an advisory on its status page. "We suspect the impact is due to a database infrastructure related change that we are working on rolling back."GitHub Status - All GitHub services are experiencing significant disruptions — At 22:59 UTC an erroneous configuration change rolled out to all GitHub.com databases that impacted the ability of the database to respond to health check pings from the routing service. As a result, the routing service could not detect healthy databases to route app