The parity.io blog is where Parity writes about JAM, Trinity, the Products Platform, the Statement Store, and proof of personhood. It’s a primary source for anyone following that work, but there’s no RSS or Atom feed to subscribe to.
I checked today, September 8:
- No
<link rel="alternate">feed-discovery tag on the blog pages. - The usual feed paths return 404: /rss.xml, /feed.xml, /atom.xml, /index.xml, /feed, /blog/rss.xml, /blog/feed.xml, and /feeds/rss.xml.
- /feed/ and /rss/ redirect to HTML pages, not feeds.
- sitemap.xml lists 118 URLs, none of them a feed.
Unless I’ve missed something, following the blog means checking it manually or setting up a workaround: changedetection.io, RSS-Bridge, or a script watching the sitemap for new posts. Those can work, but every reader has to solve the same problem, and site changes can quietly break them.
I only found yesterday’s Statement Store post because I went looking. I’d have liked it to turn up in my feed reader alongside everything else I follow.
That’s what RSS is good at. Readers can subscribe once; aggregators, archive bots, and other tools can pick up new posts directly from the source. polkadot.cloud has an rss.xml, and the Polkadot Medium publication has a feed too. It would be useful to have the same option for Parity’s own blog, rather than catching posts late or through someone else’s summary.
Since the site uses Next.js, could it generate an /rss.xml with the latest 50-100 posts (title, link, publication date, and a short summary) and advertise it with a feed-discovery tag? Depending on how the content is managed, that could be a static file generated at build time, with no separate service to run.
If there’s a reason not to offer a feed, I’d be interested to hear it. Otherwise, would Parity consider adding one?
