
Free Daily Podcast Summary
by Podcast Index LLC
The Podcast Index presents Podcasting 2.0 - Upgrading Podcasting
The most recent episodes — sign up to get AI-powered summaries of each one.
Podcasting 2.0 October 30th 2026 Episode 277 - "x402 Bitch!" ShowNotes ------------------------------------------------------------------------------------------------------------------------------------- 00 - 🚨 THE WEEK THE INDEX WENT DARK ON PURPOSE — PHP, NODE AND THE SCRAPERS Tue 20 Oct, steven: "PHP 9.2 CVE" → php.net archive. Two critical unauthenticated RCEs (Castopod lists CVE-2026-109618 & -109619, PHP below 8.4.27). Dave, 21 Oct 12:25 UTC: "Heads up, if Podcast Index api goes down at 9:00 am central time you'll know why." Then: "I've taken all the php servers offline until details come out." 16:07: "Podcast index api servers are patched and serving data again." 19:20: "After upgrading php-fpm… the fpm default config was in place so the api is running like a dawg. Restoring the pre-tuned settings now..." 20:19: "Fixed." Dave on the pile-on: "Security people are unbearable… I know you'll be up all night patching PHP servers but there are also 27 CVE's in 5 other parts of your stack that are just as bad... or worse! Sure." (amended: "security influencers") Then Node, 22 Oct: "Working on getting the web-ui repo upgraded because node.js blows worse than php. This day won't end." → "Done. Site is now on a current LTS node release and fully patched. Also blocked a large residential proxy scraper and a Chinese scraper bot in the process." → "Well, the site is down. I'm not a node guy…" (recovered). Adam: "Thank you Brother. This was a rough day for you." web-ui PR #630: Harden outbound fetches to untrusted hosts (Node CVEs) Others in the fire: Internet Archive ops (boosted by Dave) "used Claude to make fixes for our older php versions, used local models to run simulated attacks, deployed." Castopod 1.15.6 moved Docker to PHP 8.4.27. brianoflondon shut two MediaWiki sites. And Dave's timing joke: someone shipped a release "on the same day as the global PHP panic? That's like someone choosing to release their indie film on the same day as Ghostbusters." 🔍 For Dave: what was in the scraper traffic, and is the API back to its pre-tuned numbers? ------------------------------------------------------------------------------------------------------------------------------------- 01 - 🎙️ PNWR: THE PROFESSOR, LIQUID CONTENT, AND "SOMEBODY AS SMART AS ADAM CURRY" (2 clips) Podnews Weekly Review, 23 Oct — "Podcasting is liquid content now" (1h36m). Guest: Steven Goldstein, CEO/founder of Amplify Media and NYU professor. The open: Sam Sethi: "The Podcasting 2.0 and the Podcast Index, the Adam Curry and Dave Jones Project, is now six years old." James: "an awful lot of hard work going on with Dave Jones at the moment to make it easier for anybody to keep it updated." Liquid content, per Goldstein: not his term (Matthew Loran, Google DeepMind), but he brought it to podcasting: "why does content have to be in one place when people are now consuming in multiple places in multiple ways?" His model is the New York Times: print to ~400K, The Daily audio to 2–3M a day. 🎧 CLIP 1 — Sam Sethi - Adam Curry Vibe Codes His Own Podcast App, Is That The Future - POD NEWS WEEKLY REVIEW <a href="https://www.buzzsprout.com/1538779/episodes/20007510-podcasting-is-liquid-conte
Podcasting 2.0 October 23d 2026 Episode 276 - "Jackleg Leechers" ShowNotes ------------------------------------------------------------------------------------------------------------------------------------- 00 - 🚨 THE WEEK THE INDEX WENT DARK ON PURPOSE — PHP, NODE AND THE SCRAPERS Tue 20 Oct, steven: "PHP 9.2 CVE" → php.net archive. Two critical unauthenticated RCEs (Castopod lists CVE-2026-109618 & -109619, PHP below 8.4.27). Dave, 21 Oct 12:25 UTC: "Heads up, if Podcast Index api goes down at 9:00 am central time you'll know why." Then: "I've taken all the php servers offline until details come out." 16:07: "Podcast index api servers are patched and serving data again." 19:20: "After upgrading php-fpm… the fpm default config was in place so the api is running like a dawg. Restoring the pre-tuned settings now..." 20:19: "Fixed." Dave on the pile-on: "Security people are unbearable… I know you'll be up all night patching PHP servers but there are also 27 CVE's in 5 other parts of your stack that are just as bad... or worse! Sure." (amended: "security influencers") Then Node, 22 Oct: "Working on getting the web-ui repo upgraded because node.js blows worse than php. This day won't end." → "Done. Site is now on a current LTS node release and fully patched. Also blocked a large residential proxy scraper and a Chinese scraper bot in the process." → "Well, the site is down. I'm not a node guy…" (recovered). Adam: "Thank you Brother. This was a rough day for you." web-ui PR #630: Harden outbound fetches to untrusted hosts (Node CVEs) Others in the fire: Internet Archive ops (boosted by Dave) "used Claude to make fixes for our older php versions, used local models to run simulated attacks, deployed." Castopod 1.15.6 moved Docker to PHP 8.4.27. brianoflondon shut two MediaWiki sites. And Dave's timing joke: someone shipped a release "on the same day as the global PHP panic? That's like someone choosing to release their indie film on the same day as Ghostbusters." 🔍 For Dave: what was in the scraper traffic, and is the API back to its pre-tuned numbers? ------------------------------------------------------------------------------------------------------------------------------------- 01 - 🎙️ PNWR: THE PROFESSOR, LIQUID CONTENT, AND "SOMEBODY AS SMART AS ADAM CURRY" (2 clips) Podnews Weekly Review, 23 Oct — "Podcasting is liquid content now" (1h36m). Guest: Steven Goldstein, CEO/founder of Amplify Media and NYU professor. The open: Sam Sethi: "The Podcasting 2.0 and the Podcast Index, the Adam Curry and Dave Jones Project, is now six years old." James: "an awful lot of hard work going on with Dave Jones at the moment to make it easier for anybody to keep it updated." Liquid content, per Goldstein: not his term (Matthew Loran, Google DeepMind), but he brought it to podcasting: "why does content have to be in one place when people are now consuming in multiple places in multiple ways?" His model is the New York Times: print to ~400K, The Daily audio to 2–3M a day. 🎧 CLIP 1 — Sam Sethi - Adam Curry Vibe Codes His Own Podcast App, Is That The Future - POD NEWS WEEKLY REVIEW <a href="https://www.buzzsprout.com/1538779/episodes/20007510-podcasting-is-liquid-content-now" target="_bla
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 aggres
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, "Monol
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,
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
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 <b>Sunday 6 Sep:</b> "<b>My Umbrel docker containers did not survive the OS upgrade from Ubuntu 20 to 24 on my podcast rig.</b> <b>This is why I never upgrade anything.</b> I still have some Ubuntu 12 and 18 servers running." — a sentence that should be on a T-shirt at Podcast Movement. <b>Tuesday, the diagnosis, and he takes it on the chin:</b> "It was a <b>v1 to v2 docker compose transition issue</b>. It was <b>very much my fault for not RTFM before doing do-release-upgrade</b>." Plus: "doing <b>2 upgrades back to back</b> to get from LTS 20 to 24." <b>To @ericpp, same day, the two-line eulogy:</b> "<b>It's incredibly borked.</b>" → "<b>I'm closing the channel you have open to me because I'm going to have to wipe this box.</b>" — note that the lightning channel was collateral damage. That matters for §02. <b>Thursday 10 Sep, the rebuild:</b> "<b>Omarchy on the podcast rig now. Let's see how this goes.</b>" and then, shortly after, "<b>Podping gossip watcher up and running on it.</b>" <b>The genuine question underneath:</b> the podcast rig runs podping's gossip watcher. <b>What is actually load-bearing on that box</b>, 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 <b>@js to you directly, 11 Sep:</b> "@adam <b>it's like an advent calendar until the IPO — behind today's door is</b>..." and then the Anthropic threat-intelligence report. Anthropic — Detecting and countering misuse (11 Sep PDF) <b>The line JS pulled out:</b> "<b>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</b>: within hours, the ac[tors]..." <b>And the prediction, two days earlier:</b> "<b>can you _imagine_ what stunts anthropic has planned for around the IPO timeline in a few months? gonna be great.</b>" <b>The board-meeting angle:</b> every one of these reports is simultaneously a safety disclosure and a capability advertisement. <b>Publishing "our model was used to design a guided rocket" is a warning and a brochure at the same time</b> — and the IPO is in a few months. ------------------------------------------------------------------------------------------------------------------------------------- 00 - 🔥 STEP ONE OF THE SCARY STUFF — THE NEW 'PODCASTS' IDENTITY TABLE <b>The lead, and it's Dave's.</b> Wednesday 3 Sep: "#api The new <b>`podcasts` table is now being written to by default on all new incoming feeds</b> and the <b>conflict queue is being populated for merge decisions</b>. <b>This is step 1 of the scary stuff.</b> Let's hope nothing catches fire." @dave — the podcasts table goes live (3 Sep) <b>Thursday 4 Sep, step one lands:</b> "#api <b>All feed ingestion paths now use the new 'podcasts' identity table.</b> Spent the morning cleaning up a lot of old error log debris I've been neglecting for years <b>so I can have clean logs for the next step</b>." <b>😄 And the same morning he broke it and immediately confessed:</b> "#api <b>I would like to pretend (by silence) that I didn't break feed ingestion this morning for about 20 minutes</b> 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. <b>Tuesday 9 Sep, the number of the week:</b> "#api <b>Refactored the weekly database dump script</b> since it was getting slower and slower and was very old. Re-running the new one now to test. <b>I'm anticipating 4 hour run instead of 28 hours.</b>" — twenty-eight hours to four. That is the dump t
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.

Better Offline
Ed Zitron and guests explore how the tech industry’s power players shape society, for better or worse.

Public Figures
Audioboom Studios

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

Accidental Tech Podcast
Three nerds discuss technology, Apple, programming, and related topics.

supermegashow
Matt Watson & Ryan Magee

The Daily Zeitgeist
A daily comedy-news podcast where hosts break down the week’s biggest stories with sharp analysis and humor to help make sense of the chaos.

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

So, Get This
iHeartPodcasts and Bubbler

Growth Triggers: Content Marketing & AI
A marketing podcast teaching business owners how to use podcasting to generate leads, sales, and authority across competitive niches.

TWiT News (Audio)
Covers breaking tech news and product announcements from major technology companies with expert analysis.

The Nextlander Podcast
Three veteran game journalists discuss weekly gaming news, industry trends, and personal gameplay experiences.

The Best One Yet
A daily 20-minute podcast breaking down the three key business stories with sharp, accessible takes.
The Podcast Index presents Podcasting 2.0 - Upgrading Podcasting
AI-powered recaps with compact key takeaways, quotes, and insights.
Get key takeaways from Podcasting 2.0 in a 5-minute read.
Stay current on your favorite podcasts without falling behind.
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.
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.
No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by Podcast Index LLC.
Absolutely! The free plan covers up to 3 podcasts, any in the catalog. Basic raises that to 15, Pro to 40 and Max to 100. Browse our full catalog at /podcasts.
Podcasting 2.0 publishes weekly. Our AI generates a summary within hours of each new episode.
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.
Free forever for up to 3 podcasts. No credit card required.
Free forever for up to 3 podcasts. No credit card required.