Podcasting 2.0 September 25th 2026 Episode 272 - "Is this Y'all?"     00 - 🗄️ THE SCHEMA IS LIVE — AND THEN THE AGGREGATORS PICKED A FIGHT <b>Dave has already told us this one is his: "Will explain in the board meeting tomorrow."</b> <b>Mon 22 Sep — the cutover lands:</b> "#api <b>All api endpoints are now live with the new database schema.</b> Bug reports welcome. I'm tired. 😅" @dave — all endpoints live on the new schema <b>Tue 23 Sep — and now the real work:</b> "Now comes the post-deploy quality testing of the Index as a whole. <b>Now that we have an audit trail for every feed</b> we will need to <b>walk every podcast in the Index</b> to see where it stands and what metadata needs reconciling." <b>New tables in the dump:</b> "@js There are new tables in the ndjson dump now. 😉" · "@js You're the guinea pig. Let me know if anything looks off." <b>On breakage, to Mitch (Podverse):</b> "Any additional parameters should be additive. <b>The overall shape of the response should not change.</b> There *shouldn't* be any breakage unless the client is doing a Rust style strict type coercion. But, I wouldn't expect that to be common since JSON is fragile." <b>Thu 24 Sep — the brawl, in four posts:</b> 12:10 — "#api <b>Adding 2 new indexes on the feeds table.</b> Expect the api to choke for a few minutes until this completes." 14:38 — "#api <b>All out brawl with the feed aggregators this morning. I'm about to win though.</b>" 17:08 — "<b>Battle is over. The war is ongoing.</b>" 20:02 — "#api I fixed a huge problem with the feed aggregators. Based on this snapshot of our database metrics, <b>can you guess at roughly what time that happened?</b>" · 20:03 — "<b>Network throughput up. CPU and disk rate down. It's a win-win.</b>" <b>🔍 The question for Dave:</b> what were the aggregators actually doing — hammering the feeds, or something subtler that the new audit trail made visible for the first time? And what did the two indexes fix? <b>19:13 — the bug he flagged for today:</b> "#api There was a problem with <b>search ranking in the search/byterm endpoint</b> after switching the db schema. This should be fixed now. <b>Will explain in the board meeting tomorrow.</b>" <b>Loose end:</b> @ChadF, 24 Sep — "@dave looks like <b>podcaster wallet is returning the old node address</b>." Not visibly answered yet. <b>Also closed this week:</b> docs-api #160, "BUG: Wrong season number in some episodes" — season 14 coming back as 4. ------------------------------------------------------------------------------------------------------------------------------------- 01 - 🎤 GUEST: SAM SETHI — TRUEFANS, AND THE THREE FEEDS HE ASKED TO TALK ABOUT <b>He set this agenda himself.</b> 22 Sep, to Dave: "thank you my friend. When are we going to get you back on PWR and equally <b>I would love to come back on P2.0 to talk about SuperFeeds, Publisher Feeds and Network Feeds</b>." @samsethi — the ask (22 Sep) <b>📦 1. SUPERFEEDS — what he has actually shipped</b> His own definition, 19 Jul: "Traditional RSS feeds were designed to distribute podcast episodes,