[sammorrowdrums]

There is no correct answer. Having the segments go from smallest to largest or vice versa seems more logical than mid-small-large, but frankly iso8601 is clearly the most logical we have, but we’re never going to get everyone to use that outside of computer programming contexts.

Lexical sort ordering without parsing the date string is a great property.

But clearly in human terms it’s never going to be a solved issue! Nobody is looking for a solution, and everyone likes their own convention. Mutual understanding is what’s important.

The fact we have divergent date string formats is most frustrating because for many dates (up to the 12 of every month) it is ambiguous which format is in play.

[mousetree]

It's not a matter of 1password deciding which format is "correct". They just need to actually respect the user's locale settings.

[sammorrowdrums]

I agree, I was replying to the prior comment. Non-locale respecting dates are always problematic for users.

[bee_rider]

> Lexical sort ordering without parsing the date string is a great property.

Why? Why is the date even a string in the first place? It ought to be internally represented as 3 numbers. Or a Unix timestamp. Convert it to months, days, and/or years as appropriate right before printing.

[kiicia]

Never use unix time stamp as date. You don’t know time zone, you need to calculate leap years (both days and seconds), summer time etc such a “date” would immediately morph into useless random number