Notify podcast aggregators of an RSS feed update in real time via Podping instead of polling

domain: podping.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Have your hosting platform or publishing tool send a plain HTTP GET request containing the updated feed's URL to a Podping.cloud endpoint whenever the RSS feed changes or a new episode posts.
  2. Podping.cloud validates the publisher's identity, then writes the feed URL plus associated "reason" and "medium" codes as a custom JSON object onto the Hive blockchain (new block roughly every 3 seconds).
  3. Aggregators/apps watch the Hive blockchain (via a hivewriter/hivewatcher client — available for Python, Rust, and JS) instead of polling each feed individually, picking up the change within about 20 seconds.
  4. On restart, a watcher can resume a few hundred blocks back so it doesn't miss notifications that occurred while offline.
  5. Optionally declare in the feed itself that it uses Podping by adding a <podcast:podping usesPodping="true"/> element as a child of <channel>, so directories know they can poll it less frequently.

Known gotchas

Related routes

Notify the Podcast Index directly that a feed has changed using its hub/pubnotify endpoint
podcastindex-org.github.io · 5 steps · unrated
Signal a live/streaming episode in a podcast RSS feed using podcast:liveItem
podcasting2.org · 6 steps · unrated
Add OP3 open prefix analytics to a podcast RSS feed
op3.dev · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans