Discover
Podcasting 2.0
Podcasting 2.0
Author: Podcast Index LLC
Subscribed: 41Played: 1,074Subscribe
Share
Description
PC2.0 Episode #275 October 16th 2026 Live!
Pre-Boost Us!
Get Podcast Addict, Podcast Guru, CurioCaster, Podverse, Fountain and Truefans from newpodcastapps.com
208 Episodes
Reverse
Podcasting 2.0 October 16th 2026 Episode 275 - "Off The Rails"
What is the future of independent Podcast apps. OR any apps for the matter? Adam and Dave don't agree
ShowNotes
-------------------------------------------------------------------------------------------------------------------------------------
01 - 🎙️ THE ROBOT GOES ON PNWR — "I DON'T SEE THE NECESSITY FOR PODCAST APPS" (summary, no clips)
Podnews Weekly Review, 16 Oct — "Adam Curry's AI Podcast Future" (1h29m; Adam, 4:00–53:45)
Sam's setup: on our last show Adam "changed Dave Jones' mind… from a skeptic to a believer". Adam: "I went back and listened… the first thing that Dave went to was advertising. It seems like anything with podcasting always evolves around advertising, even though… we don't have advertising on our podcast."
On Muse and the "spying" story: "Muse is collecting all this data, it's making files of every single one of your friends… That is a feature, not a bug." — and the five machines at home running local models.
Sam: Reddit removed RSS and charged for its API ($43M from selling data); Lightning/L402 "worked for a while, but then… legislation and technical challenges." Will clients pay x402 to reach the Index through the MCP? Adam: "I don't see the necessity for YouTube apps, podcast apps, email apps… all clients that access all data will be some version of an agent working on the user's behalf." And: "Amazon did the stupidest thing ever by blocking Muse."
On the newsletter: "40% of all value for value revenue always comes after we send the newsletter."
On RSS: "RSS stays. It's a perfect format… no different from HTTP or SMTP." Podcast Index Robot "goes into this structured RSS feed, which is very low overhead."
On podcast apps: "Podcast apps has been probably the crappiest part of the entire podcasting business. It's truly a labor of love… Do you want to be an interim step in between the data and the user? Maybe, but I don't know." And on Godcaster: "We're in the app business too… same issues apply."
The clean-feed line: Adam had his Omarchy box build a Cleanfeed-equivalent into his playout — "I'm gonna probably cancel my subscription, which is only $36."
Sam's close: TrueFans is building "Kevin and Kelly" as experimental agents on the Index fire hose. Afterward, to James: "Adam Curry is very smart and he can use it" — but normal people won't. James: "I don't think normal people will be doing that, will they?"
And the follow-up on Mastodon. Sam posted a Fintech Times piece on agentic payments "after all the chat with Adam and Dave about micropayments 2.0 using X.402"; Adam: "The power will shift to consumer power with agentic negotiation between vendors of goods and services."
Fintech Times: the real barrier to agentic payments is not the AI
-------------------------------------------------------------------------------------------------------------------------------------
02 - 🚫 WILL APPLE LET THE ROBOT SKIP THE ADS?
aegrumet, under Adam's 274 post: "I still think you're underestimating the pressure that will fall on platforms to create and enforce TOS that forbids this stuff… the tech is ahead of the policy, and… the latter will eventually catch up."
Dave: "You're saying you think Apple will change their terms to prohibit local on device models from assisting in ad skipping?" … "Ad blockers are already allowed on the AppStore and PlayStore… a popular Reddit ad/nag blocker and things like 1Blocker for Safari… Neither Apple, nor Google serve podcast ads."
aegrumet's last word: Google and Apple "are fundamentally different with respect to ads. Hence Chrome is much more aggressive with respect to blocking the blockers. I don't see the current moment as a policy so much as a lack of one."
Sam on PNWR: "This week Apple blocked Muse, and so did Amazon" — agents doing price checks and arbitrage. TrueFans built a web application firewall off JS's bot list because AI bots were running up its MongoDB bill.
Dave on Spotify, boosted: "Spotify harnessing hundreds of dev hours and the power of 3 supercomputers to change what the like button does again."
-------------------------------------------------------------------------------------------------------------------------------------
03 - 🏷️ NAMESPACE — A FEED FOR PEOPLE, AND VIDEO IN THE ALTERNATE ENCLOSURE
podcast:person for fictional characters (discussion #498). Dave: "Makes great sense."
Nathan Gathright: propose a personGUID attribute pointing at a medium=person feed — so "Tap on a person, open up a list of their podcast appearances" works for every podcast:person tag. alecksgates: "the problem is no source of truth." Mitch: maybe a publisher or playlist feed referenced with a guid. Sam: TrueFans tried this two years ago and is "reliant on the hosts first implementing support for the person tag."
Adam replied: "SOPML!!" Mitch asked the robot what Adam meant — "Adam Curry almost certainly meant SOPML = Social OPML" — and: "thanks to transcripts and BoK, you can now communicate in mere grunts." Dave: "lol!"
Podnews ships video through the alternate enclosure (Liquid Studios pilot): Spotify, LinkedIn, TrueFans, Pocket Casts, YouTube — "Not on Apple Podcasts, sadly." Podcast Guru: works, but now needs a switch-to-video toggle "since it's not HLS." Dave: "Assuming you chose mp4 since Apple Podcasts doesn't play HLS out of the alternate enclosure yet?" James: "mp4 because that's all I can produce… I don't really want to serve HLS, given it's massively more expensive to serve." Podcast Guru: "honestly you're the first podcaster we've seen doing it. 😆"
partytime3: Nathan's agent listed the partytime parser bugs it hit; Dave: "I'll post the partytime3 code shortly and see what is still outstanding."
#794 closed: JS fixed the podcast:guid example XML with a valid UUID.
🔍 For Dave: is partytime3 out?
Last Modified 10/16/2026 14:34:17 by Freedom Controller
Podcasting 2.0 October 9th 2026 Episode 274 - "Vibe Cloning"
The Future is here! And so is the risk of spinning out. Adam & Dave go deep
<b>ShowNotes</b>
-------------------------------------------------------------------------------------------------------------------------------------
00 - 📜 1,088 LINES DOWN TO 168 — THE INDEX GETS NEW TERMS OF SERVICE
<b>Dave, 5 Oct:</b> "Podcast Index terms of service updated (finally)… The old v1.x terms were <b>90% boilerplate legalese that never accurately reflected what we wanted. I get emails weekly asking for clarification.</b>" · "The old terms of service were <b>1088 lines. The new ones are 168 lines. It's a 2-3 minute read.</b>"
Terms of Service v2.0
<b>And it is an open project:</b> "The PI terms of service are an open project just like everything else. If you think something can be worded better… just open a PR."
<b>JS found the best line:</b> "<b>Since the Service is free, our total liability to you is zero dollars.</b>" : )))))))
<b>Last week's bandwidth leak, follow-up.</b> Dave to James, 3 Oct: "rotating URLs is a good solution… Part of the issue here is <b>linode not giving any visibility into per bucket/key stats</b>. That alone probably means I need to change to a different solution." And on 6 Oct, Linode rebooted the utility server <b>in the middle of the weekly full database dump</b> — it had uploaded; "Stand down."
🔍 <b>For Dave:</b> did R2 win? And did the object-storage safeguards break James's 24-hour feed report (4 Oct)?
<b>Spam, the new tells</b> (cisene): hijacked high-profile shows republished through <b>spreaker.com</b> under a 2-5 letter owner name for ad insertion — "easy peasy spotted and killed"; and SEO spam from lawyers, dentists, roofers, gardeners treating the Index as "a cheap/free billboard". Chinese casino spam "has almost stopped". Dave flagged one himself on Apple, 8 Oct.
-------------------------------------------------------------------------------------------------------------------------------------
01 - ✂️ "DAI IS TOAST" — THE SKIP-DYNAMIC-ADS CHECKBOX IS COMING
<b>Dave, 8 Oct — the prediction:</b> "By the end of 2027, one 'tier 2' podcast app (meaning Overcast, Podcast Addict, Castro, etc) will put a <b>'Skip Dynamic Ads' checkbox</b> on their settings screen, which will remove DAI slots from podcast episodes on-device after download. And, as soon as one of them does it, <b>they will all do it.</b>" · "The writing is on the wall. DAI is too trashy and disruptive to the listening experience and the DAI ad load has become too high. <b>The podcast industrial complex will have nobody to blame but themselves.</b>" (Adam boosted it.)
<b>How, per Dave (to mikek999):</b> "On device transcription is already solid enough. Then you profile the mp3 waveform and look for anomalies that correspond to what the model thinks is an inserted advertisement… <b>Adam proved it works in real time on our last board meeting.</b>" · "You don't need to know the slot timings. It's all discernable from the transcript and waveform." · "If the tech exists, it will happen… It's why the Brave browser and uBlock Origin exists."
<b>And on 4 Oct:</b> "'Skip dynamic ads' will be a check box just like x2 speed or sleep timer… <b>I think baked in host read ads will continue. But DAI is toast imo.</b>" Sam Sethi agreed: "apps make no money from ads… <b>Spotify has legitimised ad removal.</b>"
<b>Better Offline, "Monologue: Australia's Dodgiest AI IPO Is A Pale Horse"</b> (Ed Zitron, iHeart / Cool Zone, 9 Oct). Adam: <b>"front ads cut, end ads remain."</b>
🧮 <b>What the raw feed served us this morning:</b> the file is <b>15:40</b>; the show is <b>10:08</b> (2:56–13:04). <b>Front: 2:56</b> — Oppenheimer, then four iHeart promos (What Happened to Her, Don't Lie to Me, Scam Goddess, Artists on Artists). <b>End: 2:25</b> — Chase for Business, Hulu (Jamie Foxx), BET (Tyler Perry's Sisters), a credit union, and Crown Coins Casino. <b>About 34% of the file is ads.</b> It opens and closes with "This is an iHeart Podcast. <b>Guaranteed human.</b>" The feed's own duration says 619 seconds — the content only.
<b>Last week Dave counted</b> 4.5 minutes of pre-rolls and 5 of post-rolls in a 17-minute Better Offline — "all pharma ads that don't apply to me."
<b>MinusPod is on the Index apps list</b> (web-ui #569, merged 8 Oct): "a <b>self-hosted, open-source RSS proxy that removes ad segments from podcast audio and serves a re-cut feed</b>." It mints a new podcast:guid per served feed, strips soundbite / integrity / alternateEnclosure / source / liveItem, and regenerates transcripts, chapters and duration from the cut audio.
MinusPod — Podcasting 2.0 support notes
<b>The research, today (Podnews):</b> ad load is "flashing a yellow light" — <b>54.8% of listeners say there are already too many ads; only 8.6% would tolerate more</b> to keep shows free. Social media is <b>three times</b> more effective at finding new podcasts than ads in other shows.
<b>Same story — iHeart in Podtrac's September rankings:</b> shows up from <b>20,861 to 32,741</b> in a year, yet US audience <b>down 17%</b> and US downloads <b>down 20%</b>. None of the top 5 grew. And Rogan, renewed with Spotify: about <b>15 ads per show (8% ad load)</b> per Podscribe.
<b>Meanwhile the money is up</b> (PNWR / Podnews): Podscribe US podcast ad spend <b>+20% from August, $41m</b>; WARC: online audio <b>$16.6bn</b> globally this year, +9.9%. Amazon, Alphabet and Meta take <b>60% of all ad revenue</b>.
<b>Libsyn now publishes its ad slots in the RSS feed</b> — its own namespace: two pre-rolls, two mid-rolls, first mid-roll at 620 seconds. James: the timings are for the <b>raw file</b>, so "you can't actually use this data for skipping ads"; probably for a third-party inserter like SoundStack. Sam: "Somebody has taken over Libsyn secretly… CEO of Libsyn, if you're in trouble, blink twice."
<b>PNWR on our last show</b> (today, 19:02): Sam — "Adam Curry and Dave Jones had quite an amazing show… It stripped out all the advertising, found the clip section… Dave Jones certainly felt could be <b>the end of advertising within podcasting</b>." James (hadn't heard it): "anytime we hear the end of advertising is nigh… <b>there's no real change in consumer behavior.</b>" Sam: "<b>Adam Curry will be on this show next week</b> to talk about what's going on."
<b>Leo, per csb (6 Oct):</b> TWiT's "ad sales are down to zero" after outsourcing ad sales; Club TWiT subscriptions are what keep it alive.
<b>The arms race starts:</b> marcjohanssen links "adversarial attacks" that hide audio from AI (no transcripts, no ad detection). Dave: "<b>If it can be heard it can be analyzed.</b>"
💡 The open feed was always the ad-skipper's friend. The industry spent ten years making DAI the business model — and the same transcript-and-waveform tools it sells for "brand safety" can find its slots.
-------------------------------------------------------------------------------------------------------------------------------------
02 - 🕸️ DAVE ON THE OTHER SHOW — THE PODPING MESH AND AN INDEX THAT GIVES ITSELF AWAY
<b>PNWR, 3 Oct, "In full: Dave Jones from Podcast Index"</b> — Sam waited years for it.
<b>The mesh:</b> Podping keeps writing to the Hive blockchain "just like we always have"; the new part is <b>peer-to-peer gossip</b> — "everybody's familiar with BitTorrent…" Sam: "You can't come out with words like a peer-to-peer gossip network over a mesh network and then say, that's it, ladies."
<b>To JS on Mastodon (4 Oct):</b> "It's just the same podping hive schema but <b>over Iroh gossip as the transport</b>… Any binary that speaks iroh over that gossip topic should see the traffic immediately. I can update the README with the schema and wire protocol details." — JS had asked: "is it an implementable network protocol? or does it only work with a specific binary?"
<b>Tokens for everyone:</b> "Right now you have to… email me and ask for a podping authorization token… <b>It feels too secretive, like you got to be in the club.</b>" Within the next few months: an open registration. podping.cloud is five geolocated nodes; a host just sends a GET.
<b>The big one:</b> "I have this perfect vision of the future where the podcast index becomes very decentralized… <b>we sort of work ourselves out of a job</b>, and we do not become just another directory run by a couple of dudes, instead, <b>everybody has a slice of the directory</b>." He is rewriting the aggregator to distribute <b>chunks of the database through the Podping mesh</b>, as gossip topics.
<b>On marketing the namespace</b> (Sam's "biggest disappointment" — and our section 01 last week): "I don't think that it's a marketing problem… marketing could actually produce the opposite result… <b>what you sell them with is what you sell them to.</b>" Over-promise a tag, it doesn't pan out, and "the next time you come to me… you can take a hike."
🔍 <b>For Dave:</b> how far along is the aggregator rewrite, and what is in the first database topic?
-------------------------------------------------------------------------------------------------------------------------------------
03 - 🤖 PODCAST ROBOT — WEEK ONE
<b>It works in other robots.</b> csb connected it to <b>Grok</b> (2 Oct). ChadF got a <b>Podcasting Credit Score of 84</b> — "Claude even told me what tags were missing and gave examples of how to add them." Adam: "a passing grade!!"
<b>Kolomona</b> sent the lookup URL patterns to add <b>v4vmusic.com</b> app links (publisher, playlist, album).
<b>mitch:</b> "Does the new MCP server open up the possibility for apps to add an AI option to their search pages?" Dave: "I think Adam's take is correct on this. <b>Not really intended for podcast apps unless they are already agentic based. API is still the correct thing</b> for normal podcast apps."
<b>csb: "AC is genius"</b> — the "SaaS-pocalypse": per-seat software subscriptions erode when MCP lets people run workflows inside their AI assistant. He also wants to inte
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
<b>What it says it is:</b> "Podcast Robot is a plug-in for AI assistants like Claude, ChatGPT or your own agent. Once connected, your assistant can <b>see every podcast in the world through Podcast Index</b>… plus the live signals that say when something new drops or a show goes live. <b>No account, no key, nothing to install.</b> Your podcast app stays your podcast app: Podcast Robot hands you links that open right in it."
<b>The asks it handles:</b> "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?" (<b>18,000 shows carry location</b>) · "How do I support this show?" (funding / Value4Value).
<b>Let it keep watch:</b> "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, <b>Dots</b>); a true every-15-minutes needs your own agent, <b>such as Muse</b>.
<b>💡 For podcasters: "grade my feed"</b> — Podcast Robot "tells you which Podcasting 2.0 tags you are missing and <b>what each one would let assistants do for your listeners</b>." <b>That is an answer to Sam's marketing thread in section 01:</b> 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: <b>Always-On AI Agents</b>." The page says the opposite: <b>your podcast app stays your podcast app.</b>
Last Modified 10/02/2026 14:17:57 by Freedom Controller
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, with the audio attached using the enclosure tag. Then came Podcasting 2.0, introducing <b>more than 30 new namespace tags</b>… A SuperFeed lets you combine much more than audio or video. Alongside your podcast episodes you can include <b>blog posts, publisher updates, events, premium paid content — all delivered through a single RSS feed</b>."
<b>The bit that matters for the Index:</b> SuperFeeds started (Jul 2024) as "the ability for a podcaster to <b>add any new Podcasting 2.0 tag to their existing RSS feed</b> and then publish the new TrueFans RSS feed to the Podcast Index <b>while staying with their existing host</b>" — a free claim-and-enrich service that keeps the enclosure with the original host.
<b>Where it is now:</b> two experimental tags added Apr 2026 — <b>podcast:pinned</b> and <b>podcast:store</b> — plus podroll and publisher feeds, with events and merch built on the publisher-feed pattern. "Our goal is to allow creators to <b>build a SuperFeed by picking what elements are added</b> to their RSS feed."
<b>And the anti-Patreon argument, 7 May:</b> "Apple's proprietary API for HLS video doesn't use RSS. <b>TrueFans is going the other way.</b> We are building Super RSS feeds with <b>Audio, Video and Freemium/Premium RSS in the same feed. No need for Patreon private feeds.</b>"
🔍 <b>Ask:</b> if a SuperFeed is one feed containing podcast + blog + events + merch + premium, <b>what does an app do with the items it does not understand?</b> Is there a medium or a filter, or does every app have to learn every type?
<b>📡 2. PUBLISHER FEEDS — and the pattern he keeps reusing</b>
He builds everything on remote items off the publisher feed: "<b>We will add NEW Events and Merchant tags based on the publisher feed</b>" — `<podcast:publisher><podcast:remoteItem medium="publisher" feedUrl="https://feeds.truefans.fm/rss/publishers/…" /></podcast:publisher>`
<b>Event feed proposal, 1 Aug:</b> "We are proposing a <b>new EVENT feed based on the Publisher Feed</b>" — 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.
<b>Merch — the StoreFront proposal, 31 Aug:</b> "TrueFans recently added a new experimental tag for RSS feeds called <b>Podcast:StoreFront</b>. The aim of this StoreFront tag is to <b>mirror the Funding tag</b>" — 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.
🔍 <b>Ask Dave:</b> 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?
<b>🕸️ 3. NETWORK FEEDS — the one nobody has seen yet</b>
<b>This is new.</b> He has posted publicly about SuperFeeds since 2024 and Publisher Feeds since 2024 — but <b>"Network Feeds" appears exactly once anywhere on podcastindex.social: in his 22 Sep ask</b>. There is no proposal, no example feed, no thread. <b>This is the scoop of the segment — let him define it live.</b>
🔍 <b>Ask:</b> 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"
<b>🚨 This is the live wire of the episode.</b> V4V was built on Lightning and SATs. Our guest — who has shipped a SATs wallet — is now saying the rail may be wrong.
<b>24 Sep, in his own words:</b> "We also just enabled <b>Paypal, Amazon Pay, Samsung Pay</b> to go alongside Apple/Google Pay and Bank. I am now looking at <b>Stablecoin</b> as an option. <b>I still [think] the future is micropayments direct from fan to creator but maybe not Bitcoin.</b>"
<b>Stripe Pay By Bank — TrueFans added support same day:</b> "Pay by Bank is a single-use payment method that allows customers to <b>pay directly from their bank account instead of using a card</b>… runs on banking infrastructure and takes advantage of <b>open banking APIs</b>." Caveat he flagged: "only <b>Finland and UK</b> which is odd but we will keep an eye and see if other countries get added."
<b>25 Sep 00:29, the thesis:</b> "there is still a <b>real need on the web for micropayments</b>. I think when <b>mainstream banks give customers a current/chequing account and a digital account</b> and make it easy for us to transfer money from one account to the other <b>will be the start of a wider adoption</b>."
<b>27 Jul, the post-mortem on v1:</b> "Maybe <b>v1.0 was too complex with KYC, Nostr, Alby and Moonpay</b>. I am watching <b>Stripe, Stablecoins and x.402</b>, 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."
<b>💡 But his funding tag is the purest V4V in the ecosystem — give him credit for it:</b> "The podcaster <b>only gets paid if they continue to publish</b> more episodes… Platforms like Patreon or Substack will continue to take the monthly amount <b>even if the podcaster doesn't publish</b>." The fan sets a monthly maximum; TrueFans draws from it per episode published. <b>That is value-for-value enforced in code.</b>
<b>Also:</b> if a feed has no funding tag, TrueFans turns its own on and takes <b>10% of funding transactions</b>. Worth asking how that sits with podcasters who did not ask for it.
🔍 <b>The question for the room:</b> if Pay By Bank and stablecoins do the job with less friction, <b>is Lightning still the point of V4V — or was the point always fan-to-creator with no intermediary, whatever the rail?</b>
-------------------------------------------------------------------------------------------------------------------------------------
03 - 🏛️ SAM'S THESIS — "LESS LIKE PODCAST APPS AND MORE LIKE CREATOR PORTALS"
<b>15 Sep, his four-part statement of direction:</b> "The old model was simple: <b>one creator → one podcast → one audio app</b>. That worked when podcasting was primarily about listening. But creators are building something much bigger now… the next generation of creator platforms will look <b>less like podcast apps and more like Creator Portals</b> — a single place where creators can build, engage, communicate with and monetise their communities."
<b>What is already live:</b> 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.
<b>New this month — newsletters:</b> "Starting next week we're taking another step forward with the launch of the <b>NEW TrueFans Newsletter</b>… the plan is to make the <b>same newsletter functionality available to every TrueFans creator</b>" with subscriber / deli
Podcasting 2.0 Episode 271 - "Foot Terminal"
Adam & Dave have their SCBA's on and go deep into index refactoring and ad loads!
<b>ShowNotes</b>
-------------------------------------------------------------------------------------------------------------------------------------
00 - 🔥 STEP TWO OF THE SCARY STUFF — THE ENDPOINTS FLIP TO THE IDENTITY LAYER
<b>Last week the table went in. This week the API started using it — one endpoint at a time, four days running.</b>
<b>Sat 12 Sep:</b> "#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 <b>about 11k feeds that drifted away from being in sync</b> 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."
<b>Mon night 14 Sep:</b> "#api Making some final refinements to the new api endpoints before deploying. These will be the first ones using the new podcast identity layer. 😰"
<b>Tue 15 Sep — the first flip:</b> "#api The <b>podcasts/byfeedurl</b> endpoint is deployed with the first changes to the new podcast identity layer. <b>We will do these one at a time, watching for problems.</b> You will see nothing different in the response shape under normal circumstances. The response 'feed' object's <b>`id` property now means the podcast ID</b>. The <b>`feedId` property now means the underlying feeds table row</b> 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 <b>anything else would have broken existing apps</b>. 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."
<b>Same day:</b> "#api The new <b>podcasts/byfeedid</b> endpoint is deployed. That's all for today. Will watch the logs until tomorrow." · "#api First run of the <b>itunes ID 404 reconciler</b> under the new podcast identity regime. 🤞"
<b>Thu 17 Sep:</b> "#api The <b>podcasts/byguid</b> and <b>podcasts/batch/byguid</b> endpoints are now flipped to the new db schema." · <b>Fri 18 Sep, this morning:</b> "#api The new <b>podcasts/byitunesid</b> endpoint is live."
@dave — byitunesid live (18 Sep)
<b>📝 The app developers noticed.</b> Mitch (Podverse): "listening to last week's P2.0... the <b>nextgen Podverse schema (and ogen) relies heavily on the Podcast Index IDs as basically the authority on feed uniqueness</b>. 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, <b>I'd appreciate any documentation</b>."
@mitch — the Podverse question (15 Sep)
Dave: "If I do my job right, <b>you will see nothing different and will not need to do anything</b>. 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… <b>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.</b> I'll definitely be producing docs to flesh this out further though."
<b>😄 Then the drawing:</b> "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 <b>two 'entrances' into the redirection chain</b> and the Index follows whichever one you come in on." → "<b>Paper and pen was faster than some AI agent.</b>"
@dave — the two entrances, drawn by hand (15 Sep)
The rule as Dave wrote it: "If you come in on the <b>'byid'</b> path, you start at the podcast layer and follow the redirection to the correct feed and serve it. If you come in on the <b>'byurl'</b> 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."
<b>And the MCP ask, parked:</b> @csb asked for an MCP server. Dave: "Have to get through the rollout of the new schema first. <b>Adding MCP now would just be too much confusion.</b> It's on the list for after all the new endpoints are delivered."
<b>⭐ Board questions:</b>
<b>1.</b> Four endpoints flipped in four days with nothing caught fire. <b>Which endpoints are left</b>, and which one are you most worried about — search? episodes? podping?
<b>2.</b> Walk the two entrances on air. If I hit <b>byid</b> 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?
<b>3.</b> Mitch's question is every app developer's question: <b>when do the docs land</b>, 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?
<b>4.</b> 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?
<b>5.</b> The 11k drifted IDs — human review "a little less cumbersome." <b>How many merge decisions are sitting in the conflict queue</b>, and who is the human?
-------------------------------------------------------------------------------------------------------------------------------------
08 - 🐧 OMARCHY, AND THE 'AI SUMMARIZER' EVERY PODCAST WEBSITE NOW HAS
<b>Dave went Arch.</b> 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 <b>the DHH spell</b> 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 <b>llm-insert</b> 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."
<b>📜 Dave Winer, 11 Sep 2001, reposted by JS on the anniversary:</b> "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
<b>The week:</b> 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.
<b>🛒 Tom Webster's keynote — 'Are podcasts at the front of the store?'</b> Previewing The Podcast Landscape 2026: "for the first time, <b>the top three places where people have 'ever' consumed podcasts are not dedicated podcast apps</b>. YouTube, Spotify and Netflix don't show podcasts front-and-centre… Webster compared <b>Netflix's podcasts category as the equivalent of the CD range in a Walmart</b> — 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 <b>Tower Records</b>." Rob Walch, separately: "Netflix lists just <b>1 in 67,547</b> podcasts. (And doesn't list yours.)"
Podnews — Are podcasts at the front of the store? (18 Sep)
<b>📏 The IAB: a new framework is 'not needed'.</b> Jason Adamski at the Upfront: the IAB "appears to reject a medium-agnostic measurement standard like the recently-released <b>AMP Accords</b>, 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 — <b>requires a registration with your email address to read. That's not how you set standards.</b>" He hosts the PDF himself.
Podnews — IAB: a new framework is 'not needed' (17 Sep)
<b>Dave asked the question on the instance</b> (16 Sep): "@samsethi <b>Do you still have to pay to see the actual spec?</b>" 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: "<b>Certification and I think the IP blocks as well…</b>"
<b>📋 The Podcast Study 2026</b> (Summit): "<b>45% of podcast listeners would be 'at least somewhat likely' to pay for a subscription tier to remove ads</b>; and <b>64% would sign up for email</b> from their favourite podcasters." Edison: topic, hosts and guests decide what people pick; trailer and cover art least.
<b>🎬 Video, still not a platform:</b> Podscribe at the Upfront — "<b>not one of the top 500 shows are available on all video platforms</b>: YouTube, Spotify, Rumble and HLS via open RSS." Amazon Music adds ART19, Triton Omny and Flightcast video (via the <b>alternateEnclosure</b> tag, HLS), six countries. Podscribe–Rumble attribution is "the first video platform to support a




