19 replies

1. cthos 🐱 2 min later

   @zachleat It feels a little weird to have RSS and Atom as separate categories?

   1. Zach Leatherman 3 min later

      @cthos oh… hm, why? they are different feed formats no?

      1. cthos 🐱 1 hr later

         @zachleat Technically, yes, but I don't think I have seen a feed aggregator that doesn't support both Atom and RSS 2.0 (except for Apple Podcast format) since Atom was built atop/after RSS.

         But also most CMSes just spit out both formats as if they were a single "feature"

         1. Zach Leatherman 1 hr later

            @cthos ah, yes. I mostly am curious what folks are publishing as part of their own workflows. I do see a fair number of folks publishing both RSS and Atom, for some reason!

            1. Private reply 1 day later
               1. Private reply 1 day later
2. Taylor “Tigt” Hunt 4 min later

   @zachleat Don’t get me started on how they’re all asking for encoding/escaping headaches compared to microformats

   1. Zach Leatherman 2 hr later

      @tigt this feels like you’re incentivizing me to get you started

      1. Taylor “Tigt” Hunt 2 hr later

         @zachleat HTML-in-XML (RSS/Atom) is either 40% character entities by volume or malformed, and there’s always some RSS readers that can’t seem to guess right and decide the best method is to try neither

         HTML-in JSON is 50% `\?\"` by volume and we have yet to hit the adoption curve where somebody running a reader has an angry post about doing JSON Feed right, which concerns me

         1. Zach Leatherman 2 hr later

            @tigt a ha! Have you heard of using Markdown for feed content? Does anyone do or support that?

            1. Taylor “Tigt” Hunt 4 hr later

               @zachleat Yes, and unfortunately all the consumers are AI… but if you want to try, apparently the state of the art is `link[rel=alternate][type=text/markdown]`

               1. Zach Leatherman 4 hr later

                  @tigt oh fascinating, yeah — thanks. I saw that on @matuzo’s latest: https://matuzo.at/blog/2026/html-boilerplate#link-to-markdown-optional

                  1. Taylor “Tigt” Hunt 5 hr later

                     @zachleat …I wonder if any of the scrapers bother to check if it’s not slyly-altered from the real content?

                     1. Zach Leatherman 5 hr later

                        @tigt hah! oh no

3. Koos 21 min later

   @zachleat I voted 1 but forgot that I added standard.site links for which the feed is technically not on my own site. But it's a (near) duplicate of my RSS feed

4. Scott Kingery 1 hr later

   @zachleat also h-feed
   #indieweb

5. Axel Rauschmayer 1 hr later

   @zachleat I’m only still using Atom because I started before JSON Feed existed. Now I’d probably go with JSON Feed only. Seems to be broadly supported and (at first glance) is nice and simple.

   1. Zach Leatherman 1 hr later

      @rauschma Yes! I’d leaning towards this too. Which option did you pick? Just one Atom feed?

      1. Axel Rauschmayer 2 hr later

         @zachleat One feed with one file per year (helps with incremental updates).