Podcasting 2.0 August 28th 2026 Episode 269 - "Verbal Pollution" Shownotes ------------------------------------------------------------------------------------------------------------------------------------- 00 - DATABASE SURGERY WEEK — AND THE THIRD EMERGENCY OF THE MONTH The lead, and it's Dave's: Saturday 22 Aug — "#api I'm in the middle of a big refactor with the Podcast Index database schema. If I do my job right, nobody will notice it. But, the side effect will be an overall huge increase in the consistency of the data (duplicates, url change lag, etc)." @dave — the big schema refactor (22 Aug) Wednesday night: "Podcast Index database surgery will begin in the morning." Thursday: "Step 1. Expect a brief api outage. It should last just a few minutes." — then "Done" — then "#api Adding a very large table index..." — and finally, Thursday evening: "Finished. Butt is intact." (6 favourites. The board's favourite status update of the month.) What Adam should ask: what actually changed under the hood, what does "consistency" buy an app developer in practice, and is there anything a host or an app should do differently now that duplicates and url-change lag are being cleaned up? 🔥 The other half of the week — the third emergency. Tuesday 25 Aug: "#api Linode emergency maintenance on our db host. API is down." Then: "No update as of yet. Just hard down." Then the line that is really the story: "This is the third 'emergency maintenance' event that has affected us this month. Getting kind of old." And, dryly: "I guess a reboot every few years isn't too much to ask." @dave — Linode emergency maintenance, API is down (25 Aug) Board question: three unplanned outages in one month on the host that carries the Index. Is it time to talk publicly about where the database lives, and what the fallback is? The Index is infrastructure now — other people's products go down when it does. Podping shipped twice. v0.13.0 across gossip writer, watcher and monitor — "a dynamic memory cap to address the Iroh bug" (that is last week's memory leak, now capped). Then v0.14.0 the same day — "cpu architecture in the mesh announcement messages to make determining what hardware a node is running on easier." Monitor updated too: ppmonitor.podcastindex.org. @dave — podping v0.13.0, dynamic memory cap for the Iroh bug Podping monitor Podcast Index API docs ------------------------------------------------------------------------------------------------------------------------------------- 04 - 📌 PODCASTING'S GOLDEN OPPORTUNITY: HUMAN SPEECH Your PREP note, verbatim: "For PC2.0 - Podcasting's Golden opportunity! Human speech!" — filed against a piece on how to spot AI writing. Can you learn how to detect AI writing? Here are some clues The argument: text is now cheap to fake, images are cheap to fake, and as of this year so is a voice. What is not cheap to fake is a specific human, speaking unscripted, for three hours, with a transcript and a signature chain attached. Podcasting is the only medium that ships that by default — and the namespace already carries the provenance parts. 🔥 Evidence from this week, and it is stacked: 1. Apple Music is about to start labelling. @js: "more than a third of the music Apple receives monthly is '100% AI' + usage — presumably what other humanoids would call 'listening' — of AI music on Apple Music is below 0.5%. = yes they are going to have to do something about it, starting with labelling." Read that ratio again: a third of the supply, half a percent of the demand. Billboard — Apple Music to label AI-generated music 2. Nobody can hear the difference in podcasting either. @jaybrunet, 22 Aug: "I listened to a voice clone podcast last night ('Stark Reflections') and it was surprisingly more concise and easier to follow than his previous episodes that tend to meander off in too many directions. If he hadn't said it was ElevenLabs, I wouldn't have cared or noticed the difference." 3. The scale of the flood, measured. Marco Arment said Overcast transcribes about 30,000 hours of audio per day. @js checked it against his own index: "taking a look at my 'all new episodes published' internal db for last month, the world published at least 1.4m hours of new mp3 episodes for the month, or about 46k hours a day... so if your 30k hours are unduplicated then you have excellent coverage — the long tail is very long and, these days, full of generated audio." @js — 1.4m hours of new mp3 in July, full of generated audio 4. The shame is gone. Stanley Druckenmiller, on his WSJ op-ed: "I'm not embarrassed by it... I write everything using AI now for the same reason I use a calculator when I do math problems. I don't know why this is relevant. My name is on the piece. It's my message." Notus — Druckenmiller's WSJ op-ed 5. And somebody is already building the counter-stack. Japanese publishers' Originator Profile: "OP uses cryptographic digital signature technology to create tamper-proof credentials for websites. Each ID card confirms who published the content, whether professional organizations vouch for that publisher, and information about the publisher's editorial and ethical standards." — that is a person tag with a signature on it. Nieman Lab — Japanese publishers and Originator Profile ⭐ The namespace question this asks: we have person (who), location (where), transcript (what was said, word-level, timestamped). That is three quarters of a provenance stack that no AI feed can forge cheaply. Do we need a fourth — a signed claim of human origin — or is the honest move the opposite: an AI-disclosure tag, because the liars won't use either one and the honest shows will? The V4V angle: if a third of the supply is synthetic and gets half a percent of the listening, then attention is already voting for humans. Value-for-value is the only monetisation model that pays for that directly — you cannot boost a bot you don't believe in. ------------------------------------------------------------------------------------------------------------------------------------- 02 - THE LOCATION TAG, WEEK TWO — IT IS INSIDE PRODUCTS NOW Last week we watched a dataset become a globe in 48 hours. This week the apps shipped it. Podhome, this morning: "New feature: Add a location to your show and to your episodes, and modern podcast apps can put your podcast on the map. You can also see your show on @alberto's fantastic radar.rss.io." — note show AND episode level, which is exactly the gap James flagged on the globe. @podhome — location on shows and episodes (28 Aug) Podhome location docs 😊 The demand was already there — @rgblack316, 26 Aug: "@podhome I was just about to send you a feature request to add the Location tag and logged in this morning to find it already there. 😁" TrueFans shipped search off it — @samsethi, this morning: "New location search for discovery based on @alberto radar now added to TrueFans. truefans.fm/search/" TrueFans location search 😏 And @silas had it first and said nothing — 22 Aug: "Listening to the episode and hearing them talk about radar. I have had a map thing showing podcast locations for actually like two months. Both on web and on mobile. Not yet on tv. Would be cool if I were happy with it and not still a perfectionist. I'm in the car and I actually pulled over to write this." ...and he already solved the flaw everyone else is about to hit: "I ran into that s****y browser location thing and I solved it by, on the web version, just not giving you a search near me button. Only on the phone app because that is guaranteed to have gps and an actual location — not just wherever the heck a desktop computer seemingly randomly guesses where it might be located." @silas — two months of a podcast location map The granularity problem, now with the definitive example — James Cridland on PNWR this week: "You can put a building in there, a business in there, you can put everything from the state of Queensland to Brisbane City Post Office. If you do a podcast with a pastor — as you know, somebody who used to be on MTV with big hair does — then don't just put the city where you are, put..." (← that is you and Pastor Jimmy, on air, in Australia.) ⭐ Sam Sethi's line, and it is the best summary of the project anyone gave this week: "What we're beginning to see is all the hard work from the people in the podcast 2.0 community is beginning to bear fruit now, because I see them as building blocks. The person tag, the location tag, the transcript. All of these were fundamental building blocks that now you can start to build services around, which is what we've been waiting for. And of course, the lag was waiting for the data to be filled in once the tags were available." Board question: the globe is channel-level. Podhome now writes episode-level. Does Radar (and the dataset behind it) pick up item-level locations next — and does the Index want a recommended granularity in the spec, so we stop getting podcasts located in an area 2.6x the size of Texas? radar.rss.io — the globe Podcast Index — public datasets ------------------------------------------------------------------------------------------------------------------------------------- 03 - THE PERSON TAG GETS AN ENDPOINT Dave, 22 Aug: "#api The new episodes by person endpoint: /api/1.0/episodes/byperson?q=James+Cridland&max=5. It reports directly what the [item] level [person] tags dictate." @dave — the episodes/byperson endpoint (22 Aug) James wired it into Pod News, and said so on this week's PNWR: "a very simple, possibly too simple, but a very simple person tag search, which is now integrated into the Pod News website. The first time I integrated it I didn't do it very well, but it's much better now, because I've actually followed the spec." 😄 And he name-dropped you on purpose: "if you're listening to Ad