Hey, Magnus

I have noticed that you update all entries `updated` attribute when you generate your atom feed[0]. This makes all your posts receive an "updated" status on some feed readers.

[0]: https://git.sr.ht/~kmaasrud/kmaasrud.com/tree/e87a3724f82b124bcae71bd12377db817a771090/item/bin/generate-atom#L49

--
Victor Freire

> I have noticed that you update all entries `updated` attribute when
> you generate your atom feed. This makes all your posts receive an
> "updated" status on some feed readers.

From [RFC 4287], it seems like the `updated` field is indeed meant to
indicate whenever a feed entry is changed, which is what the script is
picking up on with the `date -u -r <file>` command.

Are you finding that your feed reader is using the `updated` field as
the post date?

[RFC 4287]: https://www.rfc-editor.org/rfc/rfc4287#section-4.2.15

> From [RFC 4287], it seems like the `updated` field is indeed meant to
> indicate whenever a feed entry is changed, which is what the script is
> picking up on with the `date -u -r <file>` command.

Oh, sorry to not be more clear. If you go to your atom feed and search for "2023-11-14T07:48:29+00:00", you will see that all your entries were updated, even though not all of them have actually changed. This means that every time you write a new post, all older ones will receive the same `updated` value.

--
Victor Freire

> Oh, sorry to not be more clear. If you go to your atom feed and search 
> for "2023-11-14T07:48:29+00:00", you will see that all your entries 
> were updated, even though not all of them have actually changed.

Shit, you are totally right! Will fix ASAP.

Thanks for _noticing!_