US date format is ambiguous (MM/D/YY)

[mschmidm]

The application currently uses US date format: MM/D/YY → 03/2/26

This format is ambiguous for European users. For example, France and the UK use DD/MM/YYYY → 02/03/2026, making it unclear whether 03/2/26 means March 2nd or February 3rd.

Suggested solutions:

• Preferred: DD MMM YYYY → 16 Feb 2026 (universally unambiguous)
• Alternative: YYYY-MM-DD → 2026-02-16 (ISO 8601 standard)

Thank you for your work! :)

[rampecke]

Hey,
It actually uses your browser's default. So for me, for example, it is using a different standard, since I have everything in German in my Browser. So if you want it differently, you should set that in your browser preferences.

[mschmidm]

Thanks for the quick reply! Ah, you are right, my system and browser language is English :D

Nevertheless, I still think that it would be sensible to change to date format for everyone.

The whole application is not localized, therefore it is unexpected that this one single data point is localized. While german users will directly recognize their own date format, users with a french or english browser cannot be sure what format is being used.

Using a format like "2026-02-12" or "12 Feb 2026" for everyone would clarify this.

Another reasonable option, would be to still localize the date format for everyone, but use a date style that is not ambiguous like "medium" or "long":

const date = new Intl.DateTimeFormat(undefined, { dateStyle: "medium" }).format(new Date("2026-02-12"));

With "medium", this returns "Feb 12, 2026" for English and "12.02.2026" for German.

What do you think about this? :)