Broadcast to RSS
The oldest channel still works.
Plenty of your most technical readers still live in feed readers, and plenty of internal tools speak RSS. Every Yanib story page publishes a standards compliant feed, updated the moment you publish a release.
Free forever. No credit card.
How it works
Three steps. Two minutes.
Connect
Connect a repo; its public story page and RSS feed come with it. The feed URL is the story page URL plus /rss.xml.
Review
Releases are drafted by AI from your commits and PRs, then approved by a human, so the feed carries reviewed entries, not raw commit noise.
Broadcast
Publish once. The feed updates instantly, alongside the page, email, chat channels, and API.
Why the broadcasting layer
RSS feed is one spoke of nine. Every channel gets the same reviewed update, from one publish.
- Standards compliant XML that works in every reader and aggregator
- Full release entries in the feed, not teaser stubs
- Same reviewed content as every other channel, one source of truth
- Zero setup: the feed exists the moment the story page does
Frequently asked questions
Where is the feed URL?
Append /rss.xml to your public story page URL: yanib.dev/stories/your-repo/rss.xml. It's also advertised in the page's markup for auto discovery.
Who actually uses RSS in 2026?
Feed reader diehards, yes, but also aggregators, internal dashboards, Slack RSS apps, and monitoring tools. RSS is the lowest friction way for other software to follow your releases.
Does the feed include unpublished drafts?
No. Only published, human approved releases appear, the feed is a broadcast channel, not a firehose.