[OtomotO]

But that's exactly what I meant:

I am all for a very transparent "published at" and "last updated at"

BUT NOT in the URL

Because either you would update the URL to the last updated_at (which leads to complications if updated often, need to keep a 302 for each updated/outdated url although it's not moved permanently, rather temporarily until next update)

Or you would be stuck with the original published date in the URL and potential readers could dismiss it based on a wrong assumption (that it's outdated)

An alternative is to keep posting new entries for every update, but that gets annoying as well, because you still need to show somehow that the old versions are not the newest.

So I totally agree to be upfront about original publishing date as well as last update date, but I would not put it in the URL, not for blog posts or any other page.

[erikgahner]

Fair point. My personal preference is still for blog posts to share this information in the URL, i.e., to communicate when a blog post was published even before I click a URL.

Usually bloggers tend to write new entries if they change their mind or have any updates to previous blog posts. I personally prefer this approach rather than changing the content of old blog posts. But I agree that this might be more of a personal preference.

[OtomotO]

It may just be that we consume different bloggers is all!

I read quite a few who update texts, e.g. in the space of Rust or Webgpu

In any case, I got your point. Thanks for the respectful, interesting discussion. Have a wonderful day!

[JanNash]

This kind of wonderfully civilised and respectful discussion between people who do not see something the same way is why I love hn. Thank you both, have a good Sunday!