10 chapters across the catalog
The hosts debate whether Apple will adopt the AMP group's proposed metrics, with Dave Jones suggesting Apple rarely adopts outside specs unless they align with internal goals. They reference Apple's history with HLS video and the Podcasting 2.0 tags as examples of how the company manages its ecosystem.
Dave Jones discusses technical challenges with the Podcast Index API's "add by iTunes ID" endpoint. He details the complex logic required to handle feed URL changes and synchronization between the Index's internal Apple directory and its primary database. The goal is to ensure the Index remains a reliable fallback for apps looking up shows by their legacy Apple identifiers.
The hosts discuss the success of the AMP group's mission to shift industry focus from 60-second downloads to 30-second plays. They cite Podnews data showing Apple "plays" significantly outnumbering "downloads," which benefits advertisers and publishers by increasing reported engagement metrics.
The hosts discuss how signing would allow hosting companies to whitelist known apps like Podverse or Fountain, preventing them from being blocked during traffic spikes. They reference a past incident where Fountain was being abused by bots, which Dave Jones helped identify and resolve.
Mike Dell explains that Blueberry is developing support for Apple HLS (HTTP Live Streaming) to meet customer demand for video podcasting. He notes that video metrics will likely remain similar to audio, relying on server log files for measurement. The hosts argue that the push for video is primarily driven by a desire to tap into YouTube's advertising revenue rather than improving the medium itself.
A Bloomberg article by Ashley Carmen details the rise of "Pod Slop," referring to the flood of AI-generated podcasts on listening platforms. Alberto Bettella from RSS.com discusses the implementation of voluntary AI disclosure tags for podcast feeds. While disclosure is currently voluntary, failure to label AI-generated content could eventually lead to platform removals if it breaches terms of service regarding curation and transparency.
A plan is proposed to test download boosting services like Mopod to observe their impact on analytics via the OP3 open prefix. These services often occupy a gray area between outright fraud and legitimate marketing, providing temporary spikes in numbers without real listener engagement. Some entities use these "slopcasts" primarily for SEO purposes, leveraging the authority of the apple.com domain through podcast backlinks.
The Podcast Index aims to shift from a comprehensive inventory of every XML feed to a utility that ensures any podcast a user searches for can be found. The system currently uses a backfilling process where missed searches for feed URLs or iTunes IDs trigger the index to fetch and add the content. This strategy addresses the "slop apocalypse" by focusing on surfacing content that has demonstrated human interest.
The genesis of the Podcast Index project was to provide a source of truth independent of Apple's database and to extend RSS through a new namespace. Industry veteran Rob Greenlee reportedly characterized these efforts as "fringe," a claim the hosts dispute by highlighting the universal utility the index now provides to independent developers.
Podcast App Editorial Curation, Podcast Index and User Discovery
The discussion shifts to why more independent podcast app developers do not utilize editorial curation to delight users. While Apple and Spotify use editorial teams to push specific shows, most other apps remain neutral, which the hosts believe limits discovery. They briefly consider whether the Podcast Index should provide its own editorial suggestions or highlights to help users find quality content.
