<- All posts

Atom Feeds: They're Honking Nice

Newsletters want your email. Social media wants your attention. Atom feeds just give you the text. Here’s why web feeds are, in my opinion, best for simplicity.

By Dayton3 min read

Every time you want to follow a creator on the modern internet, you are asked to:

  1. "Subscribe to my newsletter!" Spam your email with junks that will make you miss an actually important email.
  2. "Follow me on [Platform]!" Let an engagement-maximizing algorithm decide whether or not you ever see my work.
  3. "Allow desktop notifications!" Why.

When I built this website to be Boring on Purpose, I realized something was missing. I wanted a way for people to read my thoughts without asking them to surrender personal data, download an app, or fight an algorithmic feed.

Enter the humble Atom feed.

Wait, isn't RSS dead?

People have been predicting the death of RSS and Atom since Google Reader shut down in 2013. Yet, here we are in 2026, and web feeds are here to thrive!

A web feed is the purest transaction on the internet:

  • I don't know who you are, what IP address you have, or how long you spent reading.
  • I publish a post, it shows up in your reader. In chronological order.
  • You can use NetNewsWire, Feedly, Miniflux, Thunderbird, or a custom terminal reader.

Why Atom instead of RSS 2.0?

RSS 2.0 is kind of a mess. It has multiple competing revisions, ambiguous date formats (RFC 822 vs local timezones), and quirks that make parsers sweat.

Atom (RFC 4287) was created by engineers who looked at RSS and said: "Can we please just have a sane, standardized format?"

It includes standardized ISO-8601 timestamps (2026-10-05T10:03:10Z), guaranteed unique <id> URIs for every single entry, and built-in namespace cleanliness.

Easy Implementation

Because this site doesn't have 14 microservices and a message broker running on Kubernetes, generating the feed didn't require a whole infrastructure pipeline.

It’s literally just a single dynamic route handler that

  1. Fetches the latest published posts.
  2. Loops through them to build a string of valid XML.
  3. Serves it with a Content-Type: application/atom+xml header.

Simple as hell. No Redis, and especially no WordPress plugins. If you visit /atom.xml, the server renders the XML on the fly in a few milliseconds. Simple.


The funny thing about feed readers is that humans are lazy. Nobody types the full, correct path. If someone wants to subscribe to my blog, they’ll guess:

  • oud-idk.dev/feed
  • oud-idk.dev/rss.xml
  • oud-idk.dev/feed.xml
  • oud-idk.dev/atom.xml

Instead of creating four separate endpoints, Next.js rewrites allow you to make all of them valid.

And even then, my website has a metadata that will advertise the existence of Atom that readers will pick up.

The Simple Web

We spent the better of the 21st century making web publishing needlessly complicated. We added newsletter popups, infinite scroll, engagement bait, and distributed queues to deliver blog posts.

An Atom feed is a reminder that the early web got a lot of things right.

If you like what I write, paste https://oud-idk.dev/atom.xml into your reader of choice.

Join the mailing list
Get new posts delivered to your inbox. No spam, unsubscribe anytime.