Your criticism of RSS implementation is just, but not so of Atom; Atom feeds are pretty consistently spec-correct and don’t require guessing games to parse. My

Your criticism of RSS implementation is just, but not so of Atom; Atom feeds are pretty consistently spec-correct and don’t require guessing games to parse. My experience is that the only places where interpretation of Atom feeds goes wrong is where it’s dragged down by RSS, with people coding against a library that handles both, but treating it as though it were only RSS (e.g. not handling HTML titles correctly, perhaps leading to XSS attacks). Fun fact on #3 that most people don’t know: Atom supports paginated feeds: <https://datatracker.ietf.org/doc/html/rfc5023#section-10.1 https://datatracker.ietf.org/doc/html/rfc5023#section-10.1>. No idea what library support is like. I admit it was defined in the AtomPub spec, but it should still apply to regular Atom feeds too. My own website’s feed is approaching half a megabyte with all my content ever; I’d like to make it paginated and only include the most recent ones in the first page (while still satisfying my unjustified thirst for the feed to still technically contain all the content), but as long as I’m using someone else’s static site generator that doesn’t already support that I’m probably not going to get round to implementing it.