Can we please, please – PLEASE! not make the nonsensical US date format month/day/year the default in applications? 🤦‍♂️


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.

@hugh @stragu i raise you RFC 3339, which is more likely to be what you actually mean when you say ISO 8601

@zensaiyuki @stragu on the contrary, implementations should definitely not be restricted to the mere Internet.

@hugh @stragu perhaps, but for the most part i haven’t seen any actual implementation of or enthusiasm for ISO 8601 ranges or repetition patterns, or the full range of defined formats the datetime itself can have. everything uses either icalender orl crontab formats for that stuff.

@hugh @stragu , also, people are pretty casual about seperating time and date with s space instead of a T

@hugh @stragu who cares? what does it matter? it doesn’t really, except that informal format is described by rfc3339 and not by iso8601


Not too au fait with engineering and manufacturing, I surmise?

@hugh @stragu

@0 @hugh @stragu wikipedia mentions a lot of industry support. nevertheless i have never seen anyone enthusiastic on here about dates like 2020-W36-3: a valid ISO8601 date
or P45M , another valid ISO 8601 date.

Where is “here” for you?

Here for me, for instance, the week date is pervasive in IDs for various processes as it does not reveal much exploitable info about volumes or rates of work in the time spans of interest to competitors.

@hugh @stragu

@0 @hugh @stragu “here” is social media posts cheerleading ISO 8601 dates

@zensaiyuki @hugh @stragu

I didn’t know about RFC3339, thanks. For others who don’t, here’s a quick glance using the date(1) command:

ISO 8601: date +"%Y-%m-%dT%H:%M:%S%Z" (or date -Iseconds with GNU date)

RFC 3339: date +"%Y-%m-%d %H:%M:%S%:z" (or date --rfc-3339=s with GNU date)

@virtualwolf @stragu Now do "national flags to indicate written languages"

@hugh @virtualwolf @stragu Cheers from a country with three official languages

@hugh @virtualwolf @stragu I totally agree with that one. It bothers me so much. I used to create the CMS middleware behind many a website. Our designers always chose country flags for language choice. But our neighbour country was Belgium: they speak 4 languages or more... and none of those are represented by the Belgium country flag.

@arh @stragu nope, is vexing as hell because it gets confused with mm.dd.yyyy and doesn’t sort well at all, or go home

@stragu the least confusing format which has no ambiguous counterpart is yyyy-mm-dd :)

@jackdaniel @stragu and that one results in better sorting on most default settings

@stragu I use YY/MM/DD since lexicographical order and chronological order coincide.

@stragu it's just a truncated ISO layout (YYYY/)MM/DD

@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 ; 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)

@pmevzek @stragu true. old me is old and I end up saying GMT. Now don't even think about getting onto the subject of peoples' names in applications and the US-centric "christian-name, one mandatory middle name, surname"!

@ajft @stragu incidentally, UTC is my absolute favourite standard name ever.

The Francophones wanted to call it TUC “temps universel coordonné”, everyone else wanted to call it UCT “Universal Coordinated Time”.

So they split the difference and called it UTC, which stands for both.

@LunaDragofelis @stragu Agreed, I think I replied about that. Old habit that I first learnt it as GMT and keep referring to it that way. (repeats to self, UTC, UTC, UTC..)

@stragu "American date format, invented by me it was" (Yoda)


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

@stragu ISO-8601 YYYY-MM-DD only. The euro DD-MM-YYYY is the worst, it sorts by day. At least the US one sorts by month, then day, so a 1-year archive is correct.
#date #iso8601 #hasaposse

month/day/year - American
day/month/year - European
year/month/day - International

@alm10965 @stragu The day starts at 00:00, ends at 24:00 (which is the same as 00:00 of the following day, which is why you'll never see it on a clock).

@stragu I need more accounts here to boost this. Like a few thousand more.

@stragu I lived here for most of my life at this point and it still makes no freaking sense.

@stragu you’re mostly right. At least you don’t appear to be pushing for stone as a unit of weight. That’s where I draw the line.
Sign in to participate in the conversation
Mastodon - IndieHosters

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!