Podcasting 2.0

206 Episodes

Reverse

Episode 273: "Advertising is the Horse and Buggies of Podcasting"

2026-10-0201:29:45

Podcasting 2.0 October 2nd 2026 Episode 273 - "Advertising is The Horse and Buggies of Podcasting" One topic only today - Big changes coming to podcast discovery! 05 - 🤖 PODCAST ROBOT — ADAM'S MCP SERVER FOR THE INDEX Discovery New Tag adoption podroll trailer peson location etc AEO - Ask Engine Optimization AI Assistants - Robots - Muse podcastindexrobot.com — Podcast Robot, part of Podcast Index What it says it is: "Podcast Robot is a plug-in for AI assistants like Claude, ChatGPT or your own agent. Once connected, your assistant can see every podcast in the world through Podcast Index… plus the live signals that say when something new drops or a show goes live. No account, no key, nothing to install. Your podcast app stays your podcast app: Podcast Robot hands you links that open right in it." The asks it handles: "What's new in my shows?" · "Find the part where they talk about X" (transcript search, link to the moment) · "Who was that guest? Where else is she?" (podcast:person) · "Surprise me" / what other podcasters recommend (podroll) · "What's made in Austin?" (18,000 shows carry location) · "How do I support this show?" (funding / Value4Value). Let it keep watch: "Tell me when [show] goes live" · "Watch for any episode where [person] is a guest" — it tells the assistant to check only what changed, so one check costs one or two calls. The page is honest: hosted assistants schedule hourly at best (ChatGPT, Claude Routines, Dots); a true every-15-minutes needs your own agent, such as Muse. 💡 For podcasters: "grade my feed" — Podcast Robot "tells you which Podcasting 2.0 tags you are missing and what each one would let assistants do for your listeners." That is an answer to Sam's marketing thread in section 01: not a version number, a reason — every tag is now something an assistant can do. Its links out use podcast-platform-links (GitHub) csb's prediction this morning: "AC today on Podcasting 2.0 will say: Podcast player app developers, please abandon your apps because future of Podcasting are: Always-On AI Agents." The page says the opposite: your podcast app stays your podcast app. Last Modified 10/02/2026 14:17:57 by Freedom Controller

Episode 272: "Is this Y'all?"

2026-09-2501:31:41

Podcasting 2.0 September 25th 2026 Episode 272 - "Is this Y'all?" 00 - 🗄️ THE SCHEMA IS LIVE — AND THEN THE AGGREGATORS PICKED A FIGHT Dave has already told us this one is his: "Will explain in the board meeting tomorrow." Mon 22 Sep — the cutover lands: "#api All api endpoints are now live with the new database schema. Bug reports welcome. I'm tired. 😅" @dave — all endpoints live on the new schema Tue 23 Sep — and now the real work: "Now comes the post-deploy quality testing of the Index as a whole. Now that we have an audit trail for every feed we will need to walk every podcast in the Index to see where it stands and what metadata needs reconciling." New tables in the dump: "@js There are new tables in the ndjson dump now. 😉" · "@js You're the guinea pig. Let me know if anything looks off." On breakage, to Mitch (Podverse): "Any additional parameters should be additive. The overall shape of the response should not change. 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." Thu 24 Sep — the brawl, in four posts: 12:10 — "#api Adding 2 new indexes on the feeds table. Expect the api to choke for a few minutes until this completes." 14:38 — "#api All out brawl with the feed aggregators this morning. I'm about to win though." 17:08 — "Battle is over. The war is ongoing." 20:02 — "#api I fixed a huge problem with the feed aggregators. Based on this snapshot of our database metrics, can you guess at roughly what time that happened?" · 20:03 — "Network throughput up. CPU and disk rate down. It's a win-win." 🔍 The question for Dave: 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? 19:13 — the bug he flagged for today: "#api There was a problem with search ranking in the search/byterm endpoint after switching the db schema. This should be fixed now. Will explain in the board meeting tomorrow." Loose end: @ChadF, 24 Sep — "@dave looks like podcaster wallet is returning the old node address." Not visibly answered yet. Also closed this week: 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 He set this agenda himself. 22 Sep, to Dave: "thank you my friend. When are we going to get you back on PWR and equally I would love to come back on P2.0 to talk about SuperFeeds, Publisher Feeds and Network Feeds." @samsethi — the ask (22 Sep) 📦 1. SUPERFEEDS — what he has actually shipped His own definition, 19 Jul: "Traditional RSS feeds were designed to distribute podcast episodes, with the audio attached using the enclosure tag. Then came Podcasting 2.0, introducing more than 30 new namespace tags… A SuperFeed lets you combine much more than audio or video. Alongside your podcast episodes you can include blog posts, publisher updates, events, premium paid content — all delivered through a single RSS feed." The bit that matters for the Index: SuperFeeds started (Jul 2024) as "the ability for a podcaster to add any new Podcasting 2.0 tag to their existing RSS feed and then publish the new TrueFans RSS feed to the Podcast Index while staying with their existing host" — a free claim-and-enrich service that keeps the enclosure with the original host. Where it is now: two experimental tags added Apr 2026 — podcast:pinned and podcast:store — plus podroll and publisher feeds, with events and merch built on the publisher-feed pattern. "Our goal is to allow creators to build a SuperFeed by picking what elements are added to their RSS feed." And the anti-Patreon argument, 7 May: "Apple's proprietary API for HLS video doesn't use RSS. TrueFans is going the other way. We are building Super RSS feeds with Audio, Video and Freemium/Premium RSS in the same feed. No need for Patreon private feeds." 🔍 Ask: if a SuperFeed is one feed containing podcast + blog + events + merch + premium, what does an app do with the items it does not understand? Is there a medium or a filter, or does every app have to learn every type? 📡 2. PUBLISHER FEEDS — and the pattern he keeps reusing He builds everything on remote items off the publisher feed: "We will add NEW Events and Merchant tags based on the publisher feed" — `<podcast:publisher><podcast:remoteItem medium="publisher" feedUrl="https://feeds.truefans.fm/rss/publishers/…" /></podcast:publisher>` Event feed proposal, 1 Aug: "We are proposing a new EVENT feed based on the Publisher Feed" — events in the admin dashboard appear on the podcast page; tickets sold externally or in-app via Apple Pay / Stripe. Live example: the Cheerful Earful Comedy Festival on one page. Merch — the StoreFront proposal, 31 Aug: "TrueFans recently added a new experimental tag for RSS feeds called Podcast:StoreFront. The aim of this StoreFront tag is to mirror the Funding tag" — a URL to a third-party store (Amazon, Sticker Mule, Shopify) puts a shop icon on the page. Later: products hosted in TrueFans, paid in fiat via Stripe or in SATs. 🔍 Ask Dave: is the publisher-feed-with-remote-items pattern the right substrate for events and merch, or is this three tags that each want their own medium? 🕸️ 3. NETWORK FEEDS — the one nobody has seen yet This is new. He has posted publicly about SuperFeeds since 2024 and Publisher Feeds since 2024 — but "Network Feeds" appears exactly once anywhere on podcastindex.social: in his 22 Sep ask. There is no proposal, no example feed, no thread. This is the scoop of the segment — let him define it live. 🔍 Ask: what is a Network Feed, and how is it not just a publisher feed with more members? Who owns it — the network or the shows? What happens to a show that leaves? ------------------------------------------------------------------------------------------------------------------------------------- 02 - 💳 SAM ON PAYMENTS — "THE FUTURE IS MICROPAYMENTS… BUT MAYBE NOT BITCOIN" 🚨 This is the live wire of the episode. V4V was built on Lightning and SATs. Our guest — who has shipped a SATs wallet — is now saying the rail may be wrong. 24 Sep, in his own words: "We also just enabled Paypal, Amazon Pay, Samsung Pay to go alongside Apple/Google Pay and Bank. I am now looking at Stablecoin as an option. I still [think] the future is micropayments direct from fan to creator but maybe not Bitcoin." Stripe Pay By Bank — TrueFans added support same day: "Pay by Bank is a single-use payment method that allows customers to pay directly from their bank account instead of using a card… runs on banking infrastructure and takes advantage of open banking APIs." Caveat he flagged: "only Finland and UK which is odd but we will keep an eye and see if other countries get added." 25 Sep 00:29, the thesis: "there is still a real need on the web for micropayments. I think when mainstream banks give customers a current/chequing account and a digital account and make it easy for us to transfer money from one account to the other will be the start of a wider adoption." 27 Jul, the post-mortem on v1: "Maybe v1.0 was too complex with KYC, Nostr, Alby and Moonpay. I am watching Stripe, Stablecoins and x.402, a new open payment protocol that makes internet-native micropayments…" — and the Dizzee Rascal quote: "Some people think I'm bonkers / But I just think I'm free." 💡 But his funding tag is the purest V4V in the ecosystem — give him credit for it: "The podcaster only gets paid if they continue to publish more episodes… Platforms like Patreon or Substack will continue to take the monthly amount even if the podcaster doesn't publish." The fan sets a monthly maximum; TrueFans draws from it per episode published. That is value-for-value enforced in code. Also: if a feed has no funding tag, TrueFans turns its own on and takes 10% of funding transactions. Worth asking how that sits with podcasters who did not ask for it. 🔍 The question for the room: if Pay By Bank and stablecoins do the job with less friction, is Lightning still the point of V4V — or was the point always fan-to-creator with no intermediary, whatever the rail? ------------------------------------------------------------------------------------------------------------------------------------- 03 - 🏛️ SAM'S THESIS — "LESS LIKE PODCAST APPS AND MORE LIKE CREATOR PORTALS" 15 Sep, his four-part statement of direction: "The old model was simple: one creator → one podcast → one audio app. That worked when podcasting was primarily about listening. But creators are building something much bigger now… the next generation of creator platforms will look less like podcast apps and more like Creator Portals — a single place where creators can build, engage, communicate with and monetise their communities." What is already live: host and stream audio or video, publish blogs, run live events, sell tickets, merch links, premium per-episode and per-blog pricing, a fan wallet. New this month — newsletters: "Starting next week we're taking another step forward with the launch of the NEW TrueFans Newsletter… the plan is to make the same newsletter functionality available to every TrueFans creator" with subscriber / deli

Episode 271: Foot Terminal

2026-09-1801:31:58

Podcasting 2.0 Episode 271 - "Foot Terminal" Adam & Dave have their SCBA's on and go deep into index refactoring and ad loads! ShowNotes ------------------------------------------------------------------------------------------------------------------------------------- 00 - 🔥 STEP TWO OF THE SCARY STUFF — THE ENDPOINTS FLIP TO THE IDENTITY LAYER Last week the table went in. This week the API started using it — one endpoint at a time, four days running. Sat 12 Sep: "#api I'm running a script to sync up podcasts.id and newsfeeds.id so that when a new feed is born they are in sync. During the cutover to podcasts.id as the canonical form, there were about 11k feeds that drifted away from being in sync with their podcast because of a gap in the auto_increment values. This isn't strictly necessary, it just will make human review a little less cumbersome." Mon night 14 Sep: "#api Making some final refinements to the new api endpoints before deploying. These will be the first ones using the new podcast identity layer. 😰" Tue 15 Sep — the first flip: "#api The podcasts/byfeedurl endpoint is deployed with the first changes to the new podcast identity layer. We will do these one at a time, watching for problems. You will see nothing different in the response shape under normal circumstances. The response 'feed' object's `id` property now means the podcast ID. The `feedId` property now means the underlying feeds table row that podcast is treating as canonical." @dave — byfeedurl flips (15 Sep) "It's not ideal to have the podcast id be represented as feeds.id in the new responses, but anything else would have broken existing apps. And, the meaning is still faithful to what it was before. That was always meant to be the ID of the podcasts. We just didn't have a way to logically express that." Same day: "#api The new podcasts/byfeedid endpoint is deployed. That's all for today. Will watch the logs until tomorrow." · "#api First run of the itunes ID 404 reconciler under the new podcast identity regime. 🤞" Thu 17 Sep: "#api The podcasts/byguid and podcasts/batch/byguid endpoints are now flipped to the new db schema." · Fri 18 Sep, this morning: "#api The new podcasts/byitunesid endpoint is live." @dave — byitunesid live (18 Sep) 📝 The app developers noticed. Mitch (Podverse): "listening to last week's P2.0... the nextgen Podverse schema (and ogen) relies heavily on the Podcast Index IDs as basically the authority on feed uniqueness. It sounds like we may need/want to do a substantial rewrite to account for how Podcast Index API nextgen will handle ids?… after it is settled, I'd appreciate any documentation." @mitch — the Podverse question (15 Sep) Dave: "If I do my job right, you will see nothing different and will not need to do anything. I made sure the starting point for every canonical podcast index 'podcast id' is the current live feed id. If you see some sort of drift or problem it would be a bug I need to fix… the existing podcast ID's have always identified feeds, but now they will identify podcasts. The ID's themselves will not and have not changed. I'll definitely be producing docs to flesh this out further though." 😄 Then the drawing: "It's actually kind of confusing to explain. It's easier if I draw it out on paper. It sort of needs to be visualized." → "#api These might be very hard to follow. There are two 'entrances' into the redirection chain and the Index follows whichever one you come in on." → "Paper and pen was faster than some AI agent." @dave — the two entrances, drawn by hand (15 Sep) The rule as Dave wrote it: "If you come in on the 'byid' path, you start at the podcast layer and follow the redirection to the correct feed and serve it. If you come in on the 'byurl' path, you start at the feeds layer and follow up the chain to the podcasts layer and then follow the redirection to the current canonical feed and serve that." And the MCP ask, parked: @csb asked for an MCP server. Dave: "Have to get through the rollout of the new schema first. Adding MCP now would just be too much confusion. It's on the list for after all the new endpoints are delivered." ⭐ Board questions: 1. Four endpoints flipped in four days with nothing caught fire. Which endpoints are left, and which one are you most worried about — search? episodes? podping? 2. Walk the two entrances on air. If I hit byid with an old feed ID that has since been merged into another podcast — what comes back? The new canonical feed, silently? A redirect flag? Nothing? 3. Mitch's question is every app developer's question: when do the docs land, and is there a test endpoint where a developer can throw a redirected/merged feed at it and see the new behaviour before it hits their users? 4. The itunes-ID 404 reconciler — what does it do now that a podcast can outlive its feed? Does a dead iTunes ID move to the podcast row or stay with the feed row? 5. The 11k drifted IDs — human review "a little less cumbersome." How many merge decisions are sitting in the conflict queue, and who is the human? ------------------------------------------------------------------------------------------------------------------------------------- 08 - 🐧 OMARCHY, AND THE 'AI SUMMARIZER' EVERY PODCAST WEBSITE NOW HAS Dave went Arch. Sat 12 Sep, to Aleck Gates ("Why is everyone using Omarchy? Did I miss something important? My Fedora desktop just keeps chugging along"): "There is no doubt some of it is the DHH spell some people are under. I find him irritating so my draw was just having an easy starting point (config-wise) into Arch… I also wanted Hyprland and after I went to Ubuntu 24 on that box I saw Hyprland maintainers recommend against using it on Debian distros. It came down to Arch or Nix after that." (You told the NA audience on 1901 to give the kids an old laptop and "install Omarchy.") @dave — the Omarchy thread (12 Sep) @csb's Omarchy facts of the week: "Lex has just reviewed Omarchy Linux creator" · "uses Slavic-made font: JetBrains" · "creator is EU citizen creating Omarchy in EU, you are welcome, Americans" · "can be installed from USB stick under 60 seconds." @jaybrunet shipped an llm-insert plugin for the micro editor — "non-destructive, precise editing of config files when you don't want to send your whole config to a model on OpenRouter." 📜 Dave Winer, 11 Sep 2001, reposted by JS on the anniversary: "Someday soon every home will have a weblog, and we'll have great aggregation tools that allow us to quickly assemble lists of loved ones who survived. A new button on cellphones that says 'I made it' and it flows the fact to all your concerned friends." scripting.com — 11 Sep 2001 ------------------------------------------------------------------------------------------------------------------------------------- 03 - 🗽 PODCAST WEEK NYC — WEBSTER'S 'FRONT OF THE STORE', THE IAB SAYS NO NEW FRAMEWORK, AND A 99-SECOND PNWR The week: Sounds Profitable Business Summit (Mon–Tue, 400+ people, 200 buyers), the IAB Podcast Upfront (Wed), Podcast Movement (Thu–Fri). Podnews was there all week; PNWR was 99 seconds. 🛒 Tom Webster's keynote — 'Are podcasts at the front of the store?' Previewing The Podcast Landscape 2026: "for the first time, the top three places where people have 'ever' consumed podcasts are not dedicated podcast apps. YouTube, Spotify and Netflix don't show podcasts front-and-centre… Webster compared Netflix's podcasts category as the equivalent of the CD range in a Walmart — just the most popular titles in a small selection which is hard to find; while a real podcast app like Apple Podcasts or Pocket Casts was the equivalent of Tower Records." Rob Walch, separately: "Netflix lists just 1 in 67,547 podcasts. (And doesn't list yours.)" Podnews — Are podcasts at the front of the store? (18 Sep) 📏 The IAB: a new framework is 'not needed'. Jason Adamski at the Upfront: the IAB "appears to reject a medium-agnostic measurement standard like the recently-released AMP Accords, saying 'the solution is not to build a new framework from scratch', and instead suggests… two separate standards from the IAB Tech Lab — the Podcast Measurement Technical Guidelines v2.2 and the Digital Video Served Impression Guidelines." Cridland: "The guide — and even the full press release for it — requires a registration with your email address to read. That's not how you set standards." He hosts the PDF himself. Podnews — IAB: a new framework is 'not needed' (17 Sep) Dave asked the question on the instance (16 Sep): "@samsethi Do you still have to pay to see the actual spec?" James: "You've never had to pay to see the spec. (This isn't v2.2 — which has been out for a few years — just a guideline that as far as I can see rejects the AMP Accords entirely)." Dave: "I could have sworn there was something you had to pay for. The IP block lists or something maybe?" James: "Certification and I think the IP blocks as well…" 📋 The Podcast Study 2026 (Summit): "45% of podcast listeners would be 'at least somewhat likely' to pay for a subscription tier to remove ads; and 64% would sign up for email from their favourite podcasters." Edison: topic, hosts and guests decide what people pick; trailer and cover art least. 🎬 Video, still not a platform: Podscribe at the Upfront — "not one of the top 500 shows are available on all video platforms: YouTube, Spotify, Rumble and HLS via open RSS." Amazon Music adds ART19, Triton Omny and Flightcast video (via the alternateEnclosure tag, HLS), six countries. Podscribe–Rumble attribution is "the first video platform to support a

Episode 270: YOLO Guy

2026-09-1101:33:58

Podcasting 2.0 September 11th 2026 Episode 270 - "YOLO Guy Dave waves the whitflag on agentic coding and podcasting beneifts! 01 - 😂 THE PODCAST RIG ATE ITSELF — AND IS NOW RUNNING OMARCHY Sunday 6 Sep: "My Umbrel docker containers did not survive the OS upgrade from Ubuntu 20 to 24 on my podcast rig. This is why I never upgrade anything. I still have some Ubuntu 12 and 18 servers running." — a sentence that should be on a T-shirt at Podcast Movement. Tuesday, the diagnosis, and he takes it on the chin: "It was a v1 to v2 docker compose transition issue. It was very much my fault for not RTFM before doing do-release-upgrade." Plus: "doing 2 upgrades back to back to get from LTS 20 to 24." To @ericpp, same day, the two-line eulogy: "It's incredibly borked." → "I'm closing the channel you have open to me because I'm going to have to wipe this box." — note that the lightning channel was collateral damage. That matters for §02. Thursday 10 Sep, the rebuild: "Omarchy on the podcast rig now. Let's see how this goes." and then, shortly after, "Podping gossip watcher up and running on it." The genuine question underneath: the podcast rig runs podping's gossip watcher. What is actually load-bearing on that box, and should anything that the wider ecosystem depends on be sitting on a machine you're willing to wipe on a Tuesday? ------------------------------------------------------------------------------------------------------------------------------------- 09 - 🤖 THE ANTHROPIC ADVENT CALENDAR @js to you directly, 11 Sep: "@adam it's like an advent calendar until the IPO — behind today's door is..." and then the Anthropic threat-intelligence report. Anthropic — Detecting and countering misuse (11 Sep PDF) The line JS pulled out: "These actors carried out a sustained effort to develop guided weapons, using Claude to design guidance software. They did test-fire a guided rocket. This field test appears to have failed: within hours, the ac[tors]..." And the prediction, two days earlier: "can you _imagine_ what stunts anthropic has planned for around the IPO timeline in a few months? gonna be great." The board-meeting angle: every one of these reports is simultaneously a safety disclosure and a capability advertisement. Publishing "our model was used to design a guided rocket" is a warning and a brochure at the same time — and the IPO is in a few months. ------------------------------------------------------------------------------------------------------------------------------------- 00 - 🔥 STEP ONE OF THE SCARY STUFF — THE NEW 'PODCASTS' IDENTITY TABLE The lead, and it's Dave's. Wednesday 3 Sep: "#api The new `podcasts` table is now being written to by default on all new incoming feeds and the conflict queue is being populated for merge decisions. This is step 1 of the scary stuff. Let's hope nothing catches fire." @dave — the podcasts table goes live (3 Sep) Thursday 4 Sep, step one lands: "#api All feed ingestion paths now use the new 'podcasts' identity table. Spent the morning cleaning up a lot of old error log debris I've been neglecting for years so I can have clean logs for the next step." 😄 And the same morning he broke it and immediately confessed: "#api I would like to pretend (by silence) that I didn't break feed ingestion this morning for about 20 minutes by forgetting to update the env files on the aggregator servers. But, I'm sure @js will produce s[creenshots]..." — Dave knows exactly who is watching. Tuesday 9 Sep, the number of the week: "#api Refactored the weekly database dump script since it was getting slower and slower and was very old. Re-running the new one now to test. I'm anticipating 4 hour run instead of 28 hours." — twenty-eight hours to four. That is the dump the whole developer community pulls from. Podcast Index — public datasets ⭐ The board questions, and they are the show: 1. What IS the identity table — in plain language, for an app developer? If a feed changes URL, changes host, or gets duplicated, what does the new table let the Index say that it couldn't say before? 2. The conflict queue is "being populated for merge decisions" — who makes those decisions, and is it automatic or does a human rule on it? Because merging two podcasts that are actually one podcast is exactly the kind of call that goes wrong loudly. 3. You said step one. What is step two, and is that the part where something does catch fire? 4. Twenty-eight hours to four on the dump — what changed, and does that mean the public dataset can now ship more often than weekly? ------------------------------------------------------------------------------------------------------------------------------------- Last Modified 09/11/2026 14:34:15 by Freedom Controller

Episode 269: Verbal Pollution

2026-08-2801:31:46

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 shitty 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

#box-pro-ellipsis-179131272239175{-webkit-line-clamp:2;}Podcasting 2.0