Can we please, please – PLEASE! not make the nonsensical US date format month/day/year the default in applications? 🤦♂️
PRE 👏 TTY 👏 PLEASE
And to all users of that format: it makes no sense, it's counter-intuitive, it makes collaboration frustrating, it introduces inconsistencies and errors... Just stop. Please. Use international standards.
(And don't get me started on your other units of weights, volumes and distances. Bloody hell.)
Boost if I'm right.
@stragu you’re correct insofar as asserting that this is a bad practice. incorrect insofar as assuming you will get americans to care.
@stragu and display timezones as GMT+nn, I have absolutely no w@#$@#$ idea why central mountain time is!
@ajft @stragu To stay neutral then UTC is probably better than GMT, see https://www.timeanddate.com/time/gmt-utc-time.html ; this also avoids the AM/PM format that is just confusing, like all timezones abbreviations when they are not of the format "Continent or Country/City" (sometimes even a state in the US can have 2 legal timezones at the same time, depending on the city you are in)
Also abandon feet, miles, inches, pinches, furlongs, gallons and other archaic and confusing units.
@stragu my ranking of best formats:
1. UTC unix time (for APIs and stuff)
2. ISO 8601
3. everything else
It's probably based on language. In US people when they communicate dates they seem to tell it in the order of MM-DD-YYYY while in at least two countries that I'm aware of in EU we're saying it in the order of DD-MM-YYYY, which is part of how the spoken language works.
@mvz @xnx38h @pabs @stragu Right, they're both valid as written forms of how people speak. 🙂
I think we all agree Y-M-D is great because it's sortable, unambiguous, most-significant-first, filename-friendly...
Now... US weights, volumes, distances, 12-hour time... are much more deserving of criticism 🙃
@iMartyn @Magess @pabs @stragu Brits used to say it the way Americans do but started changing in the late 19th century to align more closely with the mainland where in romance languages it was spoken with the day first. It's only the "standard" because Europe made it so. The actual ISO standard is YYYY-MM-DD. Apps should instead just adapt to the locale.
that made me check if #Niantic had fixed their US-centric date format in #PokémonGO, which I'd reported as bug #feedback to them a while ago: https://mastodon.social/@FiXato/104371032452675323
Which it looks like they did!
I mean, sure, it isn't #ISO8601, but at least the catch dates are now displayed in the device #locale, rather than whichever developer's or team lead's preferred format, which make it *my* choice, which is a win in my book.
oddly enough it still seems to work on all phones or accounts, as my wife's is still showing that ridiculous format...
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!