Free Daily Podcast Summary

Podcasting 2.0: Daily Summaries Delivered

by Podcast Index LLC

204 episodes·weekly·News, Technology, Politics

Apple Podcasts

The Podcast Index presents Podcasting 2.0 - Upgrading Podcasting

This podcast is available on Pro

Upgrade to Pro to add any podcast to your daily digest.

See Plans

Latest Episodes

The most recent episodes — sign up to get AI-powered summaries of each one.

2 days ago1h 31m
Episode 271: Foot Terminal
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
1 weeks ago1h 33m
Episode 270: YOLO Guy
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 t
3 weeks ago1h 31m
Episode 269: Verbal Pollution
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. <a href="https://www.billboard.com/pro/apple-music-to-label-ai-generated-music/" ta
Aug 21, 20261h 29m
Episode 268: Dead Hanging Safari
Podcasting 2.0 August 21st 2026 Episode 268 - "Dead Hanging Safari" It's always DNS or CORS - and how your right brain is gating bad robots Show Notes ------------------------------------------------------------------------------------------------------------------------------------- 00 - THE LOCATION TAG — SPEC TO DATASET TO GLOBE IN 48 HOURS The lead, and it's yours: Wednesday afternoon Dave posted — "There is a new locations data set on the public datasets page... The db tables are still back-filling since I updated the db and aggregators to support the new <podcast:location> tag format. After a couple of days it should be mostly complete." He cc'd @james, @alberto, @js and then @DavidMarzalC. That cc list is the whole story — within 48 hours all four had done something with it. @dave — the locations dataset post (20 Aug) The shipping trail: web-ui PR #608, "add locations export to public data sets," branch <code>public_datasets</code> → merged to master the same afternoon. This is the first public dataset built on the new location tag format rather than the old one. Then somebody built the map. By Friday morning Alberto had radar.rss.io/#globe up — a spinning globe of podcasts made in or about places on earth, drawn from the free dataset, most entries carrying full OpenStreetMap references. James put it in front of the OpenStreetMap community directly: "One for excellent people using @openstreetmap." James's review, and the two asks: "This is so cool. Really shows the power of the location tag. The globe — would be nice to add filters to that (made in vs about). Or maybe just colour the dots differently? The next trick would be some OSM lookups on the IDs to work out what the places are." 🔥 The flaw he found, and it's a good one: "One drawback is that some people have chosen 'Queensland' as a location, which is 2.6x larger than Texas." — the granularity problem in one line. A location tag is only as useful as the smallest box someone is willing to put themselves in. Dave, on seeing it — and he is in Birmingham, Alabama: "Wow, this is incredible. I already see a podcast from Birmingham that I didn't know was based here." ❤️ ❤️ Dave, Friday: "It's beautiful. I can see this data powering so many cool app and platform features." @dave — Wow, this is incredible / Birmingham (20 Aug) @dave — It's beautiful (21 Aug) The bug found by using it: @alberto and @james noticed the <code>rel</code> property missing from the export. Dave: "That column is in there but I had to add it. I bet I left it out when I copied over the episode level response build code." Then: "I found the issue. I had made the change but not deployed the new export script to production. The 'rel' property should be in there now." Also confirmed: channel-level only in that dataset, not episode-level. @dave — that column is in there but I had to add it @dave — channel level only / rel now deployed 😂 Community request of the week — @ChadF: "we need someone to add the FEMA regions to this so I can add FEMA region 3 to my podcast location." (Board: FEMA Region 6 is already broadcasting from the Heart of the Texas Hill Country.) @ChadF — add the FEMA regions Board questions: does made in vs about want to be two tags or one tag with a rel? Do we want a recommended granularity (city, not state)? And is an OSM ID lookup something the Index should do once, centrally, so every app doesn't do it badly? Podcast Index — public datasets radar.rss.io — the globe <a href="https://github.com/Podcastindex-or
Aug 14, 20261h 35m
Episode 267: Chocolove
Podcasting 2.0 August 14th 2026 Episode 267 - "Chocolove" ------------------------------------------------------------------------------------------------------------------------------------- 00 - THE SPOTIFY "SKIP AHEAD" BUTTON — THE BIG ONE What it is: Spotify is testing a button that appears on the playback screen the moment it thinks you'd want to skip — an intro, a sponsorship message, or an entire ad break. It is bigger than everything else on screen. One tap drops you at the end of the break, back in the show. Premium subscribers only, selected markets including US and UK, and only when the app is in the foreground. Who broke it: James Cridland at Pod News, 4 August 2026 — an exclusive. Spotify never announced it. Semafor and most of the trade press picked it up afterwards; Cridland noted on air this week that some of them ran it without credit. The number that makes it different from a skip button: Cridland's arithmetic — skipping a typical ad break by hand is nine presses of the 15-second button, plus a correction tap when you overshoot. Skip Ahead is one. "Some people have said, oh, but you've been able to skip for years and this is no different. But a button that only appears when it's stuff that Spotify thinks you should be skipping is a start." It skips other people's money: the button fires on third-party ads — Acast, Odyssey, the New York Times — and on ads inside Spotify's own shows. It even skipped Search Engine's read for its own paid tier, PJ Vogt pitching Incognito Mode. One half of Spotify sells advertisers reach; the other half hands listeners a button to leave. Spotify's answer, and the trapdoor in it: Spotify told Cridland it is "not affecting ad delivery." True only if delivery means to the device. Cridland: "If ad delivery is to the listener's ear, which is actually what people are paying for..." — the download still counts, the ad still gets billed, the human never hears it. Spotify's other defence: the button merely shows where other listeners already skip. Cridland: "I'm not entirely sold on that, but if that's what Spotify say, I mean they wouldn't lie." 🔥 THE LINE FOR THE BOARDROOM — read the terms of service: "What's to stop them from going, you know what, people are using that skip ahead button, why don't we just turn that on automatically? I went to have a look at the terms and conditions of Spotify. There is nothing to stop them from doing that. Nothing at all. And let's be clear, that would destroy the ad-supported ecosystem that podcasting is." Why the scale makes it existential: Spotify is 72% of all podcast downloads in the Philippines, 47% in Mexico, about a third in Australia, 75%+ in some markets. ~300 million paying subscribers plus 500 million free. Cridland on the smaller ad-strippers: "Podtastic will never be that big... they're not going to materially harm the podcast industry. This is." And it sets the precedent — if Spotify does it, every other app can say the same. The YouTube comparison, and why it fails: YouTube also lets you skip some sponsor reads — but YouTube pays creators to be there. Spotify pays nothing for an RSS show to be on Spotify. Same behaviour, opposite deal. Board question (Adam): if the ad is baked into the file and the file is fully downloaded, who exactly is the injured party — and is that an argument for the download metric or the final proof it's worthless? Timing, for the cynics: Spotify's Q2 report credited "favorable podcast impacts" with pushing its profit margin to an all-time high — in the same window it built a button to strip other people's ads. Pod News — Spotify threatens industry with ad-skipping tool Semafor — Spotify's new 'skip' button could end the podcast business as we know it Forbes — Spotify tests ad-skip button that could upend podcast advertising <a href="https://gizmodo.com/the-v
Jul 24, 20261h 33m
Episode 266: Research Velocity
Podcasting 2.0 July 24th 2026 Episode 266 - "Research Velocity" Show Notes ------------------------------------------------------------------------------------------------------------------------------------- 📌 FROM PREP.md — Adam's PC20 items Pod News — podcast app revenue (source for 'cut the apps into the money') Pod News — the ad-skipping player Board Q (Adam): "If you go to another chapter, is that a new play?" — for the AMP play=30s definition. ------------------------------------------------------------------------------------------------------------------------------------- 00 - DAVE'S WORLD: THE ALTERNATE ENCLOSURE FINALLY GETS PICKED UP + HLS-IN-RSS SURGE Take the lap: Podbean and Buzzsprout are now testing/supporting the alternate enclosure — letting other apps (Pocket Casts, Amazon Music, iHeart, TrueFans) reach the video/alt versions instead of everything vanishing into the Apple-only void. Lead the boardroom with the namespace win. HLS video in RSS is accelerating: @js — "the rate of podcast hosts publishing high-quality video in podcast feeds using HLS has gone up quite a bit, thanks mostly to Transistor and Flightcast." The open path is winning adoption; watch it live. Namespace repo status: attribution bylines merged for the block and alternate enclosure tags (PRs #772/#773). Quiet week on commits — the plumbing is holding. Dave in the wild: on the LLM-vs-tags thread — "A 'weight' is just a form of heuristic. Regression is literally built into the LLM at a fundamental level. Re-weighting a model will always regress other weights." (Continues the on-device-AI vs authored-tags fight from 265.) Also: Hover auto-renews domains 2 days out — @genebean's alert script gets a Dave thumbs-up. HLS-in-RSS tracker (livewire) Dave Winer — distributable is not distributed ------------------------------------------------------------------------------------------------------------------------------------- BM - FROM THE TIMELINE — podcastindex.social this week (JS & Dave) @js: "the rate of podcast hosts publishing high-quality video in podcast feeds using HLS has gone up quite a bit — thanks mostly to Transistor and Flightcast." (tracker: hls.livewire.io) @js: "Waves of new podcast listeners may exist, but they aren't downloading episodes via RSS, no matter how many podcast apps are being vibe-coded." @js shared Castro's "Podcast apps: a framework for dying" — his read: "well thought-out, but a bit too pessimistic imo — the next few years are going to be interesting." (Steven B: "anyone interested in the PC2.0 namespace read and consider this.") @js on Patreon's "painful update" (Conte, layoffs): "I'd love to know what change Patreon's operational market has undergone in the last six months." @js on the scraping wars: a court ruled aggregated search data (URLs, snippets, index facts) are "publicly accessible facts," not copyrightable — relevant to index/crawler rights. @js (amplifying Dave Winer): "Threads and Bluesky are not distributed. Distributable is not the same as being distributed." @dave: "A 'weight' is just a form of heuristic. Regression is literally built into the LLM at a fundamental level… one slider." — the on-device-abstraction vs authored-tags thread, continued from 265. @dave, namespace repo: merged the block-tag + alternate-enclosure attribution PRs (mid-May); no new commits this week — the action is in adoption, not spec. @csb → @dave @adam: "bros, I've just sent you $15.55 via bitcoin gram and amazingly only one split failed" — boosts still flow on-network (counter to 'streaming sats is over'). @mgdell (Mike Dell): "21 years of podcasting: the thing I don't want us to lose." Mike Dell — 21 years of podcasting Castro — Podcast apps: a framework for dying ------------------------------------------------------------------------------------------------------------------------------------- 01 - "WHAT IS A PODCAST?" — THE AMP ACCORDS PUT A FORM
Jul 17, 20261h 41m
Episode 265: Jihobbyist
Podcasting 2.0 July 17th 2026 Episode 265 - "Jihobbyist" Slop or Not! Lightning or Frightening! Adam and Dave go deep with the Boardroom after a 2 week break ShowNotes ------------------------------------------------------------------------------------------------------------------------------------- 00 - PODPING GOSSIP-WRITER → PRODUCTION + INDEX PLUMBING ------------------------------------------------------------------------------------------------------------------------------------- 01 - THE OPEN INDEX TURNS UP INSIDE AN AI SCRAPER (SUNO) @js flagged it: a hack at Suno reveals the AI music generator used PodcastIndex to do its targeting — "with the help of an online tool called PodcastIndex, Suno identified 420,000 different podcasts that had at least five 30-minute episodes and sought to download roughly 1 million hours of podcasts." Board question: the Index exists to be "free, for any use" — and here "any use" is an AI company bulk-harvesting a million hours to train on. Is that the deal working as designed, or does anything change? A live test of the open-index ethos. Ties straight to the on-device/namespace fight below and to the spam/AI-slop lane — the same extraction pressure from three directions. Hack reveals Suno scraped via PodcastIndex (404 Media) ------------------------------------------------------------------------------------------------------------------------------------- 02 - ON-DEVICE AI vs NAMESPACE TAGS — "DIDN'T YOU INVENT THE NAMESPACE?" Your own post set it off: Adam — Apple in talks to run a startup's compressed AI models on-device (PrisMML) — "More fodder for on-device features vs new tags." The core board fight of the week. 🎧 CLIPS TO PLAY — a 3-part PNWR sequence (Cridland and Sethi discussing your position; your own SOT is NOT in their show, so play + respond): 1. The jab (44.5s): recap of the Car Curious "podcast annotations" (≈ Apple timed links) debate — Nathan Gathright: LLM-from-transcript data stays the purview of players, not publishers; Sam Sethi: "Adam Curry also came in… he sees LLMs as the way for on-device abstraction of data rather than tags. And I'm like — didn't you come up with the namespace?" File: 01 - Cridland Sethi - Adam annotations, didnt you invent the namespace - PNWR.mp3 2. Sethi's thesis (55s): his actual position — fine, copy Apple, let LLMs do transcripts as a FALLBACK "if you can't be bothered," but if a creator wants to put real data in the feed, respect what the creator wants FIRST. "An LLM is a fancy autocomplete system… I'd much rather the creator is given the opportunity to do something good first." The publisher-vs-LLM argument, self-contained. File: 02 - Sethi - an LLM is a fancy autocomplete, creator first - PNWR.mp3 3. The Spurlock correction (36s): Sam apologizes for mischaracterizing @js — "I don't think we should leave it up to LLMs at all… but in practice it's going to be the app crawlers that mark shows up using hard work and drive for differentiation, not the publishers themselves." It might not be an AI LLM, but someone still has to mark the metadata up. File: 03 - Sethi - Spurlock correction, app crawlers not publishers - PNWR.mp3 Ammo for your side: @manton — his daughter's voicemail "Hi dad, this isn't an emergency" was transcribed by Apple as "this is an emergency." Player-side LLM inference is lossy; publisher-authored tags are authoritative. The case for the namespace in one anecdote. Cultural backdrop (@js, Atlantic "The End of Reading"): a postliterate generation that treats reading the source as "arbitrarily withholding information" — if the phone abstracts everything for you, who ever touches the feed? Apple + on-device AI compression (CNBC) The End of Reading Is Here (Atlantic) ------------------------------------------------------------------------------------------------------------------------------------- 03 - FUNDING NAMESPACE: STREAMING SATS COLLAPSE → APPLE CASH IN podcast:funding? Streaming sats fell off a cliff: PNWR — Sam Sethi says boosts/streaming sats are "down to pretty well zero" in July:
Jun 19, 20261h 27m
Episode 264: Podcast Plebicide
Podcasting 2.0 June 19th 2026 Episode 264 - "Podcast Plebicide" ShowNotes ------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------- Justin Jackson's post: We Have A Communication Problem ------------------------------------------------------------------------------------------------------------------------------------- 00 - PODPING.ALPHA STABLE + INDEX / PV-ALPHA HYGIENE Milestone: Dave — "I think we can safely say that podping.alpha is stable now. It's been many weeks of 100% uptime." Lead the boardroom with the win. PV-alpha 500s: @mitch + Dave debugging the "get a list of feeds that have updates over the last X" endpoint throwing 500s; @mitch adding a delay between paginated requests in case it's a too-many-requests block. Feed de-listing puzzle: Dave to @ChadF — a feed marked dead with no spam flag; aggregators de-listing it for some other reason. Open question. Iroh 1.0 — Dave flagged it: "Dialing keys instead of IP addresses." p2p networking, boardroom catnip — worth a riff with Dave. Discussion: also surface your own snags — Sovereignfeeds webhook "Unknown Error sending to Server" and ladder.podcastindex.org appearing down (to @StevenB / Dave). Iroh 1.0 Release ------------------------------------------------------------------------------------------------------------------------------------- 01 - SPAM + AI-SLOP — TOWARD A "SPAM-COP SCORE" ------------------------------------------------------------------------------------------------------------------------------------- 02 - MEASUREMENT: AMP'S 30-SECOND "PLAY," ROUND TWO AMP defined a "play" as 30 seconds; Spotify immediately adopted it. You and Dave already called 30s "bullshit" last week — push total listen time + percent-completed as the real metrics. The walkback: AMP's original press release said "30 seconds of content played… once per user per session" — and quietly DELETED "once per user per session," leaving a woolier definition. James flagged it on-page with the HTML5 del tag. YouTube is in AMP: Google confirmed YouTube "has been participating in the AMP-led conversations" — implies YouTube uses a 30s play. Apple's stance still unknown. RSS.com test (Alberto): moving the DOWNLOAD threshold 60s to 30s changed totals by ~1% — negligible. So 30s for both plays and downloads is just simpler. The HLS gotcha: playing 10s of an HLS video podcast still downloads ~60-72s, so server logs can't tell real play — only player-side instrumentation (Spotify, future Apple) can. James: it's all too "cloak and dagger." Watch July: AMP's implementation doc is due July and the group is light on technical people — needs to be real technical work, "not a sales press release." Understanding podcast stats (PodNews) ------------------------------------------------------------------------------------------------------------------------------------- 03 - BEYOND CPM — INDIE + MISSION-DRIVEN ECONOMICS Losh Moodaley ("Beyond CPM"): the indie middle class (5k-25k downloads = only ~1-1.5% of all podcasts) can't survive on CPMs. Roadmap: audience-as-economy, sell exclusivity not inventory, scale outcomes not audiences, "owners of trust, not renters of attention." Pure V4V-adjacent framing — Sam Sethi tied it straight to TrueFans activity-based value (a share or comment is value, not just dollars) and "creator portals." Easy on-ramp to your worldview. Vox Topica (Richard Fall): full-stack agency for nonprofits/mission-driven orgs — speaks engagement/reach/"depth of message," not downloads. Nonprofits resist AI voices (authenticity) but use AI for scripts/cleanup/show notes; now recommends video to ALL clients. Beyond CPM: Surviving the New Measurement Era (PodNews Daily) Vox Topica ------------------------------------------------------------------------------------------------------------------------------------- 04 - NUMBERS + MONEY MOVES --------------------

Get Podcasting 2.0 summaries in your inbox

Free AI-powered daily recaps. Key takeaways, quotes, and mentions — in a 5-minute read.

Get Free Summaries →

Free forever for up to 3 podcasts. No credit card required.

Listeners also like.

Podmastery: podcasting insights and advice for indie creators

Practical podcasting advice for independent creators aiming to grow their audience and improve production.

Public Figures

Audioboom Studios

Macworld Podcast

A weekly roundup of news, reviews, and tips focused on Apple products and the broader ecosystem.

Better Offline

Ed Zitron investigates how tech’s powerful players shape society, from crypto scams to venture capital, through interviews and critical analysis.

The Best One Yet

Daily business news explained through sharp analysis and witty commentary, delivered in concise 20-minute episodes.

Accidental Tech Podcast

Three nerds discuss technology, Apple, programming, and related topics.

Two Parents & A Podcast

Two parents navigate raising kids, building a relationship, and tackling topics from entrepreneurship to dental industry critiques.

Posting Through It

Investigative journalists explore how social media shapes modern politics through reporting, analysis, and guest interviews.

Reply All

A podcast that explores the internet and its impact on modern life through investigative stories and personal narratives.

This Week in Tech (Audio)

A weekly roundtable of tech insiders discusses the latest developments in AI, robotics, computing, and digital privacy.

Possible NOW

Explores the future of marketing, culture, and technology through conversations with innovators shaping bold new possibilities.

Upgrade

Explores how technology impacts daily life, from personal devices to digital entertainment.

About Podcasting 2.0

The Podcast Index presents Podcasting 2.0 - Upgrading Podcasting

By Podcast Index LLC

News Technology Politics

Customized Recaps

AI-powered recaps with compact key takeaways, quotes, and insights.

Straight to Your Inbox

Get key takeaways from Podcasting 2.0 in a 5-minute read.

Save Hours Every Week

Stay current on your favorite podcasts without falling behind.

Frequently Asked Questions

What is Podzilla's Podcasting 2.0 daily summary?

It's a free AI-powered email that summarizes new episodes of Podcasting 2.0 as soon as they're published. You get the key takeaways, notable quotes, and links & mentions — all in a quick read.

How does the Podcasting 2.0 podcast summary work?

When a new episode drops, our AI transcribes and analyzes it, then generates a personalized summary tailored to your interests and profession. It's delivered to your inbox every morning.

Is this an official Podcasting 2.0 product?

No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by Podcast Index LLC.

Can I get summaries of other podcasts too?

Absolutely! The free plan covers up to 3 podcasts. Upgrade to Pro for 15, or Premium for 50. Browse our full catalog at /podcasts.

How often does Podcasting 2.0 release new episodes?

Podcasting 2.0 publishes weekly. Our AI generates a summary within hours of each new episode.

What topics does Podcasting 2.0 cover?

Podcasting 2.0 covers topics including News, Technology, Politics. Our AI identifies the specific themes in each episode and highlights what matters most to you.

Start getting Podcasting 2.0 summaries tomorrow morning.

Free forever for up to 3 podcasts. No credit card required.

Get Free Summaries →

Free forever for up to 3 podcasts. No credit card required.

Podcasting 2.0: Daily Summaries Delivered

Latest Episodes

Episode 271: Foot Terminal

Episode 270: YOLO Guy

Episode 269: Verbal Pollution

Episode 268: Dead Hanging Safari

Episode 267: Chocolove

Episode 266: Research Velocity

Episode 265: Jihobbyist

Episode 264: Podcast Plebicide

Get Podcasting 2.0 summaries in your inbox

You Might Also Like

About Podcasting 2.0

Customized Recaps

Straight to Your Inbox

Save Hours Every Week

Frequently Asked Questions

Start getting Podcasting 2.0 summaries tomorrow morning.