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
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.
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).
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.
On restart, a watcher can resume a few hundred blocks back so it doesn't miss notifications that occurred while offline.
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
Podping is a notification bus, not a hosting service — you still need your publishing tool wired to a Podping writer (e.g. podping-hivewriter) or a host that already integrates it.
It was built specifically as an alternative to WebSub/rssCloud because most podcast hosts never adopted WebSub and its per-feed resubscription burden doesn't scale to millions of feeds.
Podping.cloud has historically been operated as a shared service by the Podcastindex.org community — confirm current operator/endpoint status rather than assuming one fixed permanent URL.
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?