Currently we present a long UTC timestamp..

There are not a ton of spots where cljdoc shows timestamps.

• The builds log: https://cljdoc.org/builds
• An individual build log: https://cljdoc.org/builds/80764

Times show like this: 2024-07-27T12:42:02.377362010Z

But, this format is hard for my brain to parse

I like the unambiguous yyyy-mm-dd but the T does not help and the seconds resolution is over the top.

So maybe instead...

2024-07-27 12:42:02.38

Alternative: I'm not a big fan of the commonly used last month, last week, yesterday kind of presenting of times. At least not for this use case.

But also UTC is hard to grok...

There's always that extra mental conversion.

So maybe show time in the browser's local time?

This local time would be based on user-device local time and converted client-side.
It might be nice to also somehow optionally show UTC.
Maybe on hover. The hover could also show what time zone the presented time is using.

I don't think we need to support user timezone selection in some sort of cookie preference, at least not yet.

Who will this help?

Well, at least me!

Next steps

I will probably look into this sometime soonish.