Earlier quoted context omitted.
A publisher does not want countless browsers scraping arbitrary web pages just to see if they’ve changed when they can instead offer a single lightweight end point specifically for content that is intended to be updated. If browsers started doing this scraping I can only imagine the arms race. I can only see this happening as a service. A company crawls the web—probably a search company. Their LLM classifies changes.…
This was part of the technical justification for RSS: concentrate all the redundant page hits in once place. But another reason was that parsing an article list from messy tables-based HTML was harder than it is today with HTML5. There's even a feed attribute `h-feed` available today, which effectively turns list pages into feeds. Nobody uses it. The problem with the "single lightweight endpoint" is that it has to be…
Are you referring to the microformats tags? They were never standard, and they were never meant to "turn pages into things".
Microformats, while nice and useful, were never meant to be more as compilation of certain adopted practices by the indieweb crowd.