Now AI agents need what RSS does(julienreszka.com)
julienreszka.com
Now AI agents need what RSS does
https://julienreszka.com/blog/rss-is-back-ai-agents-are-reading-it/
70 comments
This is going to happen, but it's too expensive for your LLM to do the scanning, and instead someone needs to build and maintain the index while allowing other people to subscribe to concepts. The problem is no one has sorted out the embedding space this all lives in.
I'd argue LLMs are getting cheaper, so it will get more feasible for LLMs to soon act on our behalf, bringing only what we're interested in.
Projects like OpenClaw and Hermes already show that this can work whether the source is RSS or simply a website the agent visits.
Even Google now envisions this, since they recently announced "information agents" (https://blog.google/products-and-platforms/products/search/s...) that will keep working in the background. They surely have an index they can use, but I wonder whether that's necessary? AI agents like Claude Code suggest it's possible to use simple keyword searches, without maintaining vector indexes - https://www.tigerdata.com/blog/why-cursor-is-about-to-ditch-...
It could be that soon we're gonna get a fully personalized briefing on the topics that we're interested in, or maybe a new kind of feed, replacing social media.
I'm actually working on the briefing idea myself: https://briefin.com
Projects like OpenClaw and Hermes already show that this can work whether the source is RSS or simply a website the agent visits.
Even Google now envisions this, since they recently announced "information agents" (https://blog.google/products-and-platforms/products/search/s...) that will keep working in the background. They surely have an index they can use, but I wonder whether that's necessary? AI agents like Claude Code suggest it's possible to use simple keyword searches, without maintaining vector indexes - https://www.tigerdata.com/blog/why-cursor-is-about-to-ditch-...
It could be that soon we're gonna get a fully personalized briefing on the topics that we're interested in, or maybe a new kind of feed, replacing social media.
I'm actually working on the briefing idea myself: https://briefin.com
keywords are a start but not enough imo - consider a concept subscription such as "any of my political representatives making statements about firearm control"
That's why I reached for Apples own local LLM to fool with similar ideas like this: https://pageforth.com. Apple is better than I expected at this. Right now it filters through things like hacker news articles and whatever else you point it at to summarize and find things that match your interests. Apple's LLM reminds me of Claude like 3 years ago. It's weak for sure. But useful for small dose kind of problems.
Agree on RSS as the right shape — and worth adding the cost angle nobody's
quantified here yet. Having an LLM read a 50KB HTML page is ~$0.03 of
gpt-4o input. Polling 1000 sources hourly = ~$720/day, almost all of it
tokenizing layout chrome the model throws away. RSS-shaped feeds drop
that 90%+ because they strip to deltas. The harder blocker is the supply
side though — publishers earn pennies per human pageview from ads and ~$0
from agent polls, so unless feeds become licensed paid endpoints, the
publisher incentive runs against your "publish an RSS feed for your
content" recommendation. Just like that :)
I have almost 40 feeds I subscribe to and they're my primary way of getting information I care about without being exposed to ads or other things I don't want to see.
What are your favorite feeds?
https://theonlyblogever.com/blogroll opml file included!
These are my top ones:
Protesilaos: https://protesilaos.com/codelog.xml and https://protesilaos.com/commentary.xml
HN: https://hnrss.org/frontpage
Sacha Chua: https://sachachua.com/blog/feed/index.xml
David Revoy: https://www.davidrevoy.com/feed/rss
Davep: https://blog.davep.org/feeds/all.atom.xml
xkcd: https://xkcd.com/atom.xml
YouTube - Michelle Khare: https://www.youtube.com/feeds/videos.xml?channel_id=UCGGZ_PO...
YouTube - TmarTn2: https://www.youtube.com/feeds/videos.xml?channel_id=UC36MGPf...
Protesilaos: https://protesilaos.com/codelog.xml and https://protesilaos.com/commentary.xml
HN: https://hnrss.org/frontpage
Sacha Chua: https://sachachua.com/blog/feed/index.xml
David Revoy: https://www.davidrevoy.com/feed/rss
Davep: https://blog.davep.org/feeds/all.atom.xml
xkcd: https://xkcd.com/atom.xml
YouTube - Michelle Khare: https://www.youtube.com/feeds/videos.xml?channel_id=UCGGZ_PO...
YouTube - TmarTn2: https://www.youtube.com/feeds/videos.xml?channel_id=UC36MGPf...
TIL you can get RSS feeds for YouTube channels. Thanks for this!
You're welcome. You can also turn any subreddit into a RSS feed: https://arkvis.com/blog/2026-04-16_interesting-finds.html
Google should bring back Google Reader. But make it only for bots. And then drop it again once it gets popular.
What's old is new again. The solution RSS offered was structure for an otherwise unstructured challenge (trying to figure out updates on a site). That value grew exponentially when connected to AI (providing the signals of when do I need to look at this site/podcast again). Smart marketing.
I wouldn't limit it to RSS. They need any structured data (JSON, XML/RSS, CSV etc.).
Systems and agents need to monitor and extract public web content into fresh structured data for their ingestion, intelligence workflows and analysis.
* Shameless plug * Our data infrastructure layer for businesses and AI turns continuously updated websites into a stream of structured data.
https://newsloth.com
Systems and agents need to monitor and extract public web content into fresh structured data for their ingestion, intelligence workflows and analysis.
* Shameless plug * Our data infrastructure layer for businesses and AI turns continuously updated websites into a stream of structured data.
https://newsloth.com
I built a site that's similar in concept to Hacker News, but is entirely fed by RSS feed content, that is then bullet-pointed summarized on the article page: https://engineered.at/
But I also extract topics automatically from the content too with LLMs, to allow for dynamic topic pages that users can separately subscribe to to tune their feeds.
Haven't promoted it much, but it's pretty amazing what you can do for a couple bucks a month. And my main thesis with this site is that by locking the content to only rss feeds of known blogs, you dramatically reduce the spam submission risk (basically eliminate it). Doesn't handle the spam comment side of things, but that's a different problem.
EDIT: I also open sourced a Rails engine I made to power this site if anyone is interested: https://github.com/dchuk/source_monitor
But I also extract topics automatically from the content too with LLMs, to allow for dynamic topic pages that users can separately subscribe to to tune their feeds.
Haven't promoted it much, but it's pretty amazing what you can do for a couple bucks a month. And my main thesis with this site is that by locking the content to only rss feeds of known blogs, you dramatically reduce the spam submission risk (basically eliminate it). Doesn't handle the spam comment side of things, but that's a different problem.
EDIT: I also open sourced a Rails engine I made to power this site if anyone is interested: https://github.com/dchuk/source_monitor
This looks great, I've wanted something like this for a while. Finding how to click through to the actual item in the feed was a high point of friction for me.
I went to a topic and then clicked on the header of something I was interested in expecting to be brought to the blog post directly. Needing to click on that same title again to be brought to the post was unintuitive to me, I searched around the page, went back and forth a few times and eventually figured it out.
As a user I would love to be able to click directly through to the article FROM the topic feed. I would expect that the comments is a URL to the page that the header currently brings me to. This would match my expectations from using sites like reddit/HN.
A one or two liner summary directly on the topics feed would be really great I think.
I went to a topic and then clicked on the header of something I was interested in expecting to be brought to the blog post directly. Needing to click on that same title again to be brought to the post was unintuitive to me, I searched around the page, went back and forth a few times and eventually figured it out.
As a user I would love to be able to click directly through to the article FROM the topic feed. I would expect that the comments is a URL to the page that the header currently brings me to. This would match my expectations from using sites like reddit/HN.
A one or two liner summary directly on the topics feed would be really great I think.
Great feedback, should be straightforward to make happen. I’ll try to implement tonight.
As a sysadmin hosting a few blogs, do you mind sharing what IP ranges you crawl from? Or what agent your requests use? Thank you.
I presume you’re politely asking in order to block? Which is fine, I get it. On my phone right now but can update later.
I do want to ask though (and I should make this clear in a FAQ or something): the way I check RSS feeds uses adaptive scheduling, so I intentionally don’t check feeds of sites too rapidly. Then the summarization is based on the full article content but I never render that full content on the site (to avoid traffic hijacking concerns). Given that: what’s the concern?
I do want to ask though (and I should make this clear in a FAQ or something): the way I check RSS feeds uses adaptive scheduling, so I intentionally don’t check feeds of sites too rapidly. Then the summarization is based on the full article content but I never render that full content on the site (to avoid traffic hijacking concerns). Given that: what’s the concern?
I do appreciate you addressing the concerns about traffic hijacking, but at the same time I really don't like having my content run through a text mangler like an LLM. I get the use case, but at the end of the day it's my content and I'm a bit prickly.
That said, I'm not necessarily planning to immediately block your crawlers, I intend to just add them to a list I maintain for personal reference. I'm mostly interested in correlating the crawling traffic that I see with various sources, I have been gathering data about crawling activity and sources that I display on an embedded map on my site. I have caddy annotate traffic with a header indicating what the crawler is, and if the fleet behaves nicely then they don't get added to the blocklist.
That said, I'm not necessarily planning to immediately block your crawlers, I intend to just add them to a list I maintain for personal reference. I'm mostly interested in correlating the crawling traffic that I see with various sources, I have been gathering data about crawling activity and sources that I display on an embedded map on my site. I have caddy annotate traffic with a header indicating what the crawler is, and if the fleet behaves nicely then they don't get added to the blocklist.
Interesting. in terms of "crawling", the way the engine I built works is by default it's just polling the rss feed of a site on an adjusting cadence like any other rss feed reader. On some sites, the engine can do a follow up scrape of the article link from the rss feed if the full content of the article isn't provided in the rss feed. So it's not real crawling, more fetching/scraping if necessary.
But I hear you.
But I hear you.
Your browser is not supported.
Please upgrade your browser to continue.
That’s…bizarre. Let me take a look
EDIT: just checked in firefox, I don't see an issue. can you email me at [email protected] and maybe I can debug with you?
EDIT: just checked in firefox, I don't see an issue. can you email me at [email protected] and maybe I can debug with you?
I just noticed the same thing.
UA being blocked for example:
Allowed:
UA being blocked for example:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0
Allowed:
Opera/9.80 (Windows NT 6.1; U; zh-tw) Presto/2.7.62 Version/11.01
Opera/9.80 (Windows NT 5.1; U; cs) Presto/2.7.62 Version/11.01
Mozilla/5.0 (Windows NT 5.1) Gecko/20100101 Firefox/14.0 Opera/12.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 14; rv:140.0) Gecko/20110101 Firefox/140.0
Getting
If I set my UA to "FUCKIT" I can use the site perfectly fine. Why is there a User Agent Filter that disables the whole website? This should be maybe a warning, not a complete block.
406 browser not supported
If I set my UA to "FUCKIT" I can use the site perfectly fine. Why is there a User Agent Filter that disables the whole website? This should be maybe a warning, not a complete block.
you know, I had setup some analytics filtering based on geoip because I was getting crazy spam traffic from Chine and Singapore, but that should only be affecting analytics not the whole site. Mind if I ask where you're located? (you can email me privately if preferred: [email protected])
Europe
IP address has no effect on the User Agent block though...
IP address has no effect on the User Agent block though...
Re: Rate Limits, see
https://rachelbythebay.com/w/2024/05/27/feed/
but coming from an aggressively anticommercial world view. She collects evidence that real world feed readers don't implement RSS correctly
https://rachelbythebay.com/w/2026/02/23/readers/
Her problems are the problems of a polling-based protocol and really if she does not like the RSS protocol she should stop publishing it and stand up an ActivityPub or PubSubHubBub service instead.
A big part of the value of Google Reader and the ecosystem around it was that Google could poll your RSS feed once and everyone could read it... A huge win for the Rachels!
https://rachelbythebay.com/w/2024/05/27/feed/
but coming from an aggressively anticommercial world view. She collects evidence that real world feed readers don't implement RSS correctly
https://rachelbythebay.com/w/2026/02/23/readers/
Her problems are the problems of a polling-based protocol and really if she does not like the RSS protocol she should stop publishing it and stand up an ActivityPub or PubSubHubBub service instead.
A big part of the value of Google Reader and the ecosystem around it was that Google could poll your RSS feed once and everyone could read it... A huge win for the Rachels!
> Her problems are the problems of a polling-based protocol and really if she does not like the RSS protocol she should stop publishing it and stand up an ActivityPub or PubSubHubBub service instead.
Bit odd to take potshots at a third party blog on this discussion, why single out Rachel?
And more to the point, the dynamics here might be due to RSS being polling-based, but if feed readers implemented the RSS logic correctly it wouldn't matter nearly as much, would it?
Bit odd to take potshots at a third party blog on this discussion, why single out Rachel?
And more to the point, the dynamics here might be due to RSS being polling-based, but if feed readers implemented the RSS logic correctly it wouldn't matter nearly as much, would it?
(1) Rachel complains more than most. Most people realize it is easier for you to speed up your server/lower your costs than to expect people to implement RSS "correctly"
(2) You can use a cache or be correct, pick one! I think of all the lame cache busting methods that are still in use because it took web browsers more than 15 years to get caching mostly right.
(3) If you'd been reading Rachel as opposed to asking why I pointed Rachel out your questions would be answered!
(4) Polling based systems come in two speeds: too fast and too slow and it is possible to be both at the same time
(2) You can use a cache or be correct, pick one! I think of all the lame cache busting methods that are still in use because it took web browsers more than 15 years to get caching mostly right.
(3) If you'd been reading Rachel as opposed to asking why I pointed Rachel out your questions would be answered!
(4) Polling based systems come in two speeds: too fast and too slow and it is possible to be both at the same time
"Rael"
(1) is gender-proportionate
(2) Helps people to see that the phenom is more general. applies to any quasisocial SaaS that has an underappreciated hardtech moat or 90% learn-by-doing experts go for suboptimal tradeoffs which noobs would never consider.
(3) Maybe "complains" should be "insists", or even softer "maintains"
(1) is gender-proportionate
(2) Helps people to see that the phenom is more general. applies to any quasisocial SaaS that has an underappreciated hardtech moat or 90% learn-by-doing experts go for suboptimal tradeoffs which noobs would never consider.
(3) Maybe "complains" should be "insists", or even softer "maintains"
[deleted]
we spent a decade killing structured feeds in favor of algorithmic timelines and now we're rebuilding them because the algorithms need structured feeds. the circle of life, but for protocols.
You mean scraping instead of reading it? Reddit does not like the sound of that at all and are mulling to remove RSS support due to scrapers [0]
[0] https://www.reddit.com/r/modnews/comments/1tq9vxo/protecting...
[0] https://www.reddit.com/r/modnews/comments/1tq9vxo/protecting...
Well yeah if they provide open access to content then AI labs wouldn’t have to pay them for bull access.
Never dropped it
https://technex.us/.rss
https://github.com/hparadiz/technexus/blob/release/src/Contr...
I would enjoy a JSON based refresh of the format.
https://technex.us/.rss
https://github.com/hparadiz/technexus/blob/release/src/Contr...
I would enjoy a JSON based refresh of the format.
This is why I love HN
I guess if you want your content all slurped up and served as coming from AI with no backlinks.
Anyone know the best practices for keeping AI crawlers off your RSS feeds? I know robots.txt works for the well-behaved bots. Other tools like interstitial captchas don't as the feed readers break if you send them anything but XML.
Putting just the post intro in the feed and linking to the website feels like a safer approach, assume you have bot protections on the website, but that's a poor experience for people who want to read in their feed reader.
Putting just the post intro in the feed and linking to the website feels like a safer approach, assume you have bot protections on the website, but that's a poor experience for people who want to read in their feed reader.
I have some aggressive filters in Caddy that block the worst offenders by CIDR range, and also filter by user agent to remove any honest facebook and amazon bots. Otherwise, maybe strong rate limits by IP?
Edit:
Longer term, the approach might be - provide a separate RSS feed with full content but gated by a query parameter, then only give that URL to known-good consumers via email verification or patreon subscription, etc.
It would suck that people would have to pay more to consume content in their preferred way, but depending on your needs it might be a reasonable compromise.
Edit:
Longer term, the approach might be - provide a separate RSS feed with full content but gated by a query parameter, then only give that URL to known-good consumers via email verification or patreon subscription, etc.
It would suck that people would have to pay more to consume content in their preferred way, but depending on your needs it might be a reasonable compromise.
I kinda don't like RSS because I often want like a whole blog archive downloaded if I add a new feed and it usually has limits how far back of posts it will download (randomly configured by each site)
Unless someone has a fix of whatever settings I've been using
Unless someone has a fix of whatever settings I've been using
Sorry, I don't have a solution. But I use RSS for everything, and I can confidently say: RSS is not designed for your use case.
For the Premium Archive tier, NewsBlur attempts to download a blog's entire backlog to backfill stories, whether it's exposed through paging or RFC 5005. Here's more info about how NewsBlur does it: https://blog.newsblur.com/2022/07/01/premium-archive-subscri...
I had a similar issue where I wanted to read a newly-followed blog from the beginning instead of the point in time when I started to follow, so I created https://refeed.to/
I use Elfeed for Emacs and it stores the history as you download updates so you can always go back and read an old post.
Indeed, the simplicity and structure behind RSS perfectly fits agentic AI. Web 4.0 (or Web 5.0) would definitely use a protocol whose principles might be similar to RSS.
>RSS was declared dead in 2013
Where? Not within the homelab space.
Where? Not within the homelab space.
They probably meant it hyperbolically, but RSS was on a downward slope during that period. The recent uptick is fascinating.
https://trends.google.com/explore?q=%2Fm%2F0n5tx&date=all&ge...
https://trends.google.com/explore?q=%2Fm%2F0n5tx&date=all&ge...
>The recent uptick is fascinating
With US techs harvesting people's data, subscription mess, cars that are no longer cars but computers on wheel, and now AI, even folks with bare minimal knowledge are self hosting things.
All you need is a second hand dirty cheap Dell SFF computer from eBay, install Proxmox on it and even if it comes with only 8GB, you can still spin up a few Proxmox LXC containers (small like Docker but far better).
People are going back to buying physical media, old model of things, wired headphones is all time high.
MP3 players are all time high, no phone, no subscription, just music.
90s, early 2000s is so back and is a good thing, people themselves are putting a hard break on technology.
With US techs harvesting people's data, subscription mess, cars that are no longer cars but computers on wheel, and now AI, even folks with bare minimal knowledge are self hosting things.
All you need is a second hand dirty cheap Dell SFF computer from eBay, install Proxmox on it and even if it comes with only 8GB, you can still spin up a few Proxmox LXC containers (small like Docker but far better).
People are going back to buying physical media, old model of things, wired headphones is all time high.
MP3 players are all time high, no phone, no subscription, just music.
90s, early 2000s is so back and is a good thing, people themselves are putting a hard break on technology.
No, 2013 was demise of Google Reader, which was at the time very good and very accessible so it was how a lot of people used RSS
I must add that I self-host FreshRSS to fetch news and GitHub repos updates so I can update my stuff, everything in-house, controlled by me.
RSS makes life so much easier, some only provide the bare minimal while others, provide the whole post so I can read everything right there without opening a website.
Also, some podcast support it so I have a list of podcast that I list and can go back without having to go from website to website.
One place to govern them all, RSS still king.
RSS makes life so much easier, some only provide the bare minimal while others, provide the whole post so I can read everything right there without opening a website.
Also, some podcast support it so I have a list of podcast that I list and can go back without having to go from website to website.
One place to govern them all, RSS still king.
AI agents don't need RSS. What they need is some representation in text. The XML/RSS markup is completely unnecessary.
> The same logic will now extend to any written content that agents need to reliably consume.
Get your rapacious hands away from my website please.
> and actively degrades programmatic access.
That's your problem. You choose these tools. If they can't function without ripping everyone else off then why do you persist in using them?
Get your rapacious hands away from my website please.
> and actively degrades programmatic access.
That's your problem. You choose these tools. If they can't function without ripping everyone else off then why do you persist in using them?
The issue with RSS is that it doesn't allow to show ads. That is why the RSS reader was killed by Google.
Nowadays AI agents also don't read ads. Let's see how that is going, but the ad industry isn't amused about that.
Nowadays AI agents also don't read ads. Let's see how that is going, but the ad industry isn't amused about that.
i mean, i still read hacker news primarily via RSS in feedly. i kind of never stopped using it, and everybody is much more generous with their feeds nowadays than back in google reader times. bearblog, etc. RSS rules
I think now more than ever humans need RSS, so we can curate what enters our information feed as the social media experiment continues to degenerate.
...And Semantic Web.
I'm not sure why I keep reading HN, 99% of the content is uninteresting, probably 99.9% now that every article is about AI. maybe I just like clicking on things.