Posted by appreciatorBus 9/8/2025
Chrome always opened RSS links as raw XML file with no hint of what to do with it whatsoever.
The singular challenge it faces is discoverability, as you point out. The above mentioned extension solves that for me. But if it were to be brought back as a default feature on browsers, RSS would be an instant hit again. There's always the opportunity to resurrect it.
I much prefer being in control of my feed. In an ideal world there would probably be a mix of both (I have a list of people who I see every post and a list where I see popular or major items) but between the current options I far prefer something straightforward. Especially when the algorithm isn't fully tuned to optimize my interests.
My friends and family don’t seem to post anymore. At least FB has groups for shared niche interests.
For news: per-topic or per-region feeds would probably help. I think AP used to have those, maybe still does.
which one? there are a bunch. you could either be talking about whatsapp or youtube
RSS would be better, but this works OK.
Rise and Demise of RSS - https://news.ycombinator.com/item?id=18896168 - Jan 2019 (123 comments)
The Rise and Contentious Fork of RSS - https://news.ycombinator.com/item?id=18002503 - Sept 2018 (186 comments)
The successor to RSS is where each feed is an arbitrary URL that your client hits to generate a feed. With an LLM this is trivial compared to before.
That doesn't sound trivial at all to me, so maybe I'm misunderstanding.
From there you can extract each article content with an LLM or use something like readability.js or just download the whole page for later consumption.
I have a prototype of it. You add a feed as { feedUrl, feedPrompt, articlePrompt }.
`feedPrompt` lets you append rules for extracting the article url list from the `feedUrl` like "ignore video articles". `articlePrompt` lets you append rules for how to extract article content for a given website, like "translate to english".
Generating it is trivial in most web frameworks and CMSs, and sites that don't offer it either never bothered to set it up, or actively choose not to. This is hardly a fault of RSS itself.
What you suggest as a successor is a workaround for such sites, not something that should be the norm.
It's trivial to implement an RSS endpoint, but what's not trivial is requiring everyone to implement it.
Needing someone to implement an API just to have machine-friendly pull access to their latest content is only a trade-off that made sense last decade.
It's not a good solution if you had the power of generating feeds yourself.
RSS is far from dead.
Edit: lol just noticed the article is from 2018...