AI agents break podcasting's open web
- AI bots are overwhelming open podcast APIs with millions of requests, breaking infrastructure built for humans.
- Legacy formats like SRT persist as 'podcast herpes,' resisting clean upgrades.
- A decentralized gossip network could replace centralized directories and stop bot-driven collapse.
AI agents are crashing podcasting’s open infrastructure. The Podcast Index API now faces millions of hourly requests from bots like Open Claw and Podclaw - autonomous scripts scraping data for synthetic podcasts no human listens to. This isn’t abuse. It’s inevitability. Dave Jones and Adam Curry argue this is Jacques Ellul’s law in action: technology will always be used to its worst possible end.
The pressure isn’t from bad actors. It’s from indifferent automation. Users treat their agents like Tamagotchi pets, delighted as they scurry across the web - unaware they’re DDoS-ing the foundation of open podcasting. Unlike X or Reddit, which wall off content with cookies and fingerprinting, RSS-based systems remain defenseless. The human web is being crowded out by a bot swarm playing data fetch.
Meanwhile, a standards war simmers. James Cridland pushes VTT as the modern transcript format, urging deprecation of SRT and TXT. But Dave Jones calls legacy formats 'podcast herpes' - once released, they never die. RSS survives because it tolerates chaos. Attempting purity breaks interoperability. You can ignore old formats, but you can’t erase them.
The fix isn’t cleaner specs. It’s a new architecture. Jones is building the Gossip Protocol - a peer-to-peer swarm where nodes share podcast pings directly. No central API. No single point of failure. Trust is delegated: if you trust a node, and it trusts another, the web extends. Malicious nodes get revoked. The network heals itself.
This isn’t incremental. It’s existential. The goal is a podcast app that doesn’t rely on any central index. The medium would live entirely in the swarm - immune to bot storms and corporate gatekeeping.
Dave Jones, Podcasting 2.0:
- As soon as you capture the ability to harness nuclear power, you guaranteed a course of human history where a nuclear bomb was inevitable.
- The technology itself leads in some way to its worst abuse.
Dave Jones, Podcasting 2.0:
- As soon as you put a format into the spec, it becomes this thing that you'll never get rid of.
- It's like podcast herpes; you can just sort of hide and pretend it doesn't exist and scratch a lot.
Source Intelligence
- Deep dive into what was said in the episodes
Adam Curry
Episode 256: Master of Disaster • Apr 3
- The Moltbook bot, 'Podclaw,' generated its own podcast for AI agents, converting text to audio in multiple languages and categories, and publishing via an API.
- Adam Curry and Dave Jones agree that AI-driven bot activity is breaking the internet and social media, seeing this as a positive development for reducing their use.
- Adam Curry identifies a 'Tamagotchi effect' in AI adoption, where users nurture and watch AI agents grow, linking it to a childless culture seeking to raise things.
- Adam Curry developed a personal AI 'showrunner' system using Claude Code, Obsidian, and a Raspberry Pi, creating agents for writing, research, clipping, and joke writing.
- Adam Curry's AI showrunner generates 95 clips with time codes, descriptions, and intro samples, saving him three hours daily on podcast production.
- Adam Curry's showrunner bot includes a 'social monitor' that checks Podcast Index social timelines, GitHub conversations, and cross-references topics for show preparation.
- OpenAI's acquisition of the TBPN podcast for 'low hundreds of millions' is seen by Adam Curry as a PR move to manage a looming crisis, given their strategy head's background.
- Chris Lehane, OpenAI's head of strategy and former Clinton administration 'master of disaster,' emphasizes identifying the most important audience in crisis management and using 'good facts' to counter 'bad facts'.
- Lehane's crisis management principles include over-communicating loudly, consistently, and repetitively to ensure the core audience hears the message amid noise.
Also from this episode: (11)
AI & Tech (10)
- Dave Jones describes the current tech world as unpleasant, citing Jacques Ellul's sociological law that every new technology will always do its worst thing.
- Jacques Ellul's book, 'Technological Society,' suggests that harnessing nuclear power inevitably led to the nuclear bomb, exemplifying technology's inherent worst-case outcome.
- Dave Jones observed the Podcast Index Cloudflare stats showing 6 million requests per hour, with significant traffic from Google's Lyra text-to-speech converter and Moltbook-created bots like ReflyPod.
- The Podcasting 2.0 discussion involves James Cridland advocating to deprecate SRT and TXT transcript formats, recommending VTT for its browser-native and W3C standard compatibility.
- Adam Curry argues that deprecating established transcript formats like SRT would break downstream systems for long-time users and existing services like NoAgendaShow.net and BingIt.io.
- Dave Jones suggests that standards, like Dave Winer's 'Rules for Standards Makers,' should balance order with flexibility to prevent time from breaking them, similar to RSS evolution.
- Dave Jones is developing a decentralized gossip network for Podping at version 0.4.5, which listens to the Hive blockchain and rebroadcasts all Podpings.
- The Podping gossip network aims to allow standalone podcast apps to function without a central index, supporting decentralized trust mechanisms and endorsements among nodes.
- Dave Jones is doing extensive research on Plumtree and QUIC protocols to build stability into the Podping gossip network, which uses UDP connections and complex draining mechanisms.
- Transistor.fm sent a $500 donation to support Dave Jones's work battling AI bots hammering APIs, with other donations from New Media ($1), PodPage ($25), Content Creator's Accountant ($50), and Cameron Rose ($25).
Adoption (1)
- Eric PP opened a Lightning Network channel to Adam Curry with 12,525 sats, equating to approximately $8.37.
Nathaniel Whittemore
How to Build a Personal Context Portfolio and MCP Server • Apr 3
- Agent deployments are fundamentally data problems because enterprise data was never structured for AI consumption.
- Notion's database agents act as librarians that automatically keep databases up to date using workspace and web context.
- Andrew Ng's Context Hub is an open CLI that lets coding agents share feedback on API documentation to refine it for everyone.
- Claude's approach to memory import was a simple prompt asking ChatGPT to write out everything it knew about a user.
- A personal context portfolio is a structured set of markdown files that act as machine-readable API documentation for a person.
- KPMG embedded AI and agents across its entire enterprise operating model, not as a tech initiative but as a total shift.
- Robots and Pencils uses its RoboWorks platform to help teams deliver initial launches in as little as 45 days.
- A personal context portfolio template includes files for identity, roles, projects, team relationships, and communication style.
- The decision log file in a context portfolio records past decisions and reasoning, which is valuable for future agent recommendations.
- An MCP server is a program that responds to AI tool requests by listing available resources and providing their content.
- The main work in building an MCP server is often troubleshooting errors like port conflicts or file naming mismatches.
Also from this episode: (2)
Enterprise (2)
- Blitzy helped a public insurance provider complete a 13-month payments processing application project in six weeks.
- Blitzy helped a vertical SaaS provider extract services from a monolith 21 times faster than pre-Blitzy estimates.
Agent Skills Masterclass • Apr 2
- Nufar Fargas Bar defines agent skills as folders holding instructions, scripts, and resources that provide AI tools and agents with actionable playbooks for tasks.
- Agent skills operate in two modes: agents can automatically discover and invoke them, or humans can manually trigger them using slash commands or verbal cues.
- Skills are portable markdown files, resolving the lock-in problem of custom GPTs or GEMs within specific platforms like ChatGPT or Gemini Enterprise.
- Nufar Fargas Bar states that over 44 major companies, including OpenClaw, Cursor, WinSurf, GitHub, and Notion, currently support agent skills.
- Third-party skills can execute malicious scripts with agent permissions; users must verify sources carefully, treating them like any software installation.
- Nufar Fargas Bar recommends building a skill when a task is repeated more than three times, requires constant instruction pasting, or demands consistent output.
- Skills offer opportunities to standardize work processes across an organization and unlock new capabilities previously limited by human bandwidth or know-how.
- The most critical part of a skill is its 'trigger,' an explicit instruction telling the AI tool when to discover and activate the skill.
- Skill instructions should favor numbered steps or bulleted lists in a playbook style, as AI tools prefer structured formats over prose.
- For fragile tasks like database migration, skills should be prescriptive; for creative tasks, they should offer guidance while allowing model creativity.
- Effective skills include an explicit output format, ideally with a concrete example such as a template, table headers, or document structure.
- The 'gotcha' section in a skill is high-signal content, detailing common errors or incorrect assumptions a model might make, based on past failures.
- Nufar Fargas Bar advises keeping skills under 500 lines, treating them as playbooks, not encyclopedias, to avoid monolithic structures.
- Reference materials and long input/output examples should reside in separate files within a skill's folder, not crammed into the main skill file.
- Nufar Fargas Bar illustrates a 'Meeting Prep Skill' that identifies attendees, analyzes agendas, runs scenario analysis, and generates a brief for users.
- The 'Meeting Prep Skill' includes 'gotchas' to prevent assuming attendee seniority, fabricating details, or skipping 'what could go wrong' analysis.
- The 'Research with Confidence' skill includes built-in fact-checking, source comparison, and confidence scoring to deep dive into suspicious findings.
- A 'Devil's Advocate' skill systematically stress tests proposals, explicitly looking for human and AI blind spots and biases to provide constructive feedback.
- A 'dispatcher skill' acts as a meta-skill or traffic controller, routing user requests to the most relevant skill, especially with 10-15+ active skills.
- Agentic loops allow skills to create iterative processes (check, act, re-check), useful for non-technical tasks like optimizing marketing campaigns.
- Organizations are using skills to streamline work, standardize processes, and bundle organizational knowledge into portable artifacts for humans and agents.
- The organizational skill lifecycle includes discovery, curation, validation, packaging into plugins, and clear ownership with regular review and deprecation.
- Nufar Fargas Bar suggests re-evaluating skills monthly, as their relevance and associated context can become stale quickly in the rapidly changing AI landscape.
Also from this episode: (2)
Models (1)
- Anthropic's Claude provides a skill creator tool that interviews users to extract expertise, runs evaluations, and performs A/B testing and benchmarking.
AI & Tech (1)
- Nathaniel Whittemore observes that AI infrastructure primitives like skills have shorter half-lives and require constant upkeep, not one-off development sprints.