YYYY.MM.DD_HH24MI.SS

e.g.

2025.09.02_1830.33

you know EXACTLY when the timestamp is referring to.

remove the time part you still got a pretty clean date 2025.09.02 which is also computer sort friendly.

the only missing component is the Timezone which I find pretty stupid TBH, because as a big Space Sci-fi fan, there needs to be a universal timecode system which is universal in the literal sense. Well technically it can never be, relativity and all, but you get what I mean..

also while we are at it, we should start teaching kids 12 digit number system, so that we get rid of the pesky decimal with a more efficient duodecimal.

Oooh, and make year 13 months with each month exactly 28 days, and the fractional remainder at the end of solar cycle is just a blackout timescape that nobody acknowledges collectively throughout the world.

annnnnnnd that's enough lemmy for the day

As a filmmaker I'm incredibly upset that they flipped the image, it's like it's breaking the 180° rule but worse.

I prefer %a, %d %b %Y %T %Z because of legacy support

>>> time.strftime("%a, %d %b %Y %T %Z")
'Tue, 02 Sep 2025 14:06:16 GMT'

I do DDMMMYYYY, 02SEP2025. It is from Good Documentation Practices (GDP).

How does it make sense? Calendars aren't set up by date number, they are set up by month. You need to know which month you're talking about to get to the right date.

1. It’s currently October 2nd, 2025. MM-DD-YYYY

2. It’s currently the 2nd of October, 2025. DD-MM-YYYY

3. It’s currently 2025, October 2nd. YYYY-MM-DD

4. It’s currently 2025 the 2nd of October. YYYY-DD-MM

First one is my go to.

YYYY-MM-DD gang rise up!

Any answer other than ISO 8601 is a red flag

YYYY-MM-DD

:hh:mm:ss optional

YYYY/MM/DD is good for file locating in a single folder.

Use ISO 8601 or get out.

Except, don't actually use ISO 8601 because the T in the middle looks stupid.

ISO 8601 is the only true answer.

YYYYMMDD is the best. Easiest to sort.