Lmst

@tykling but #ISO8601 has so many nice things that aren't in #RFC3339 /o\
https://ijmacd.github.io/rfc3339-iso8601/

https://ijmacd.github.io/rfc3339-iso8601/

So you clicked on a thrilling showdown between RFC 3339 and ISO 8601, only to be whisked away to a text file on GitHub. 🤦‍♂️ Because who doesn't love a riveting debate about time formats with all the excitement of watching paint dry? ⏳🥱
https://ijmacd.github.io/rfc3339-iso8601/ #RFC3339 #ISO8601 #TimeFormats #TechDebate #GitHubFun #HackerNews #ngated

RFC 3339 vs. ISO 8601

https://ijmacd.github.io/rfc3339-iso8601/

#HackerNews #RFC3339 #ISO8601 #DateFormats #TimeStandards #TechDiscussion

Nein, auch DMY ergibt keinen Sinn. Bitte hört auf, das Meme zu teilen.

#ISO8601 #RFC3339

Die Datums- und Zeitformate 1999-12-31 23:59:59,
12/31/1999 11:59:59 PM und 31.12.1999 23:59:59 im Vergleich. Die Stellenwerte sind als Schichten einer Pyramide dargestellt.

Nur das erste Format hat eine sinnvolle Reihenfolge.

The author of this date format reference is my new hero! https://ijmacd.github.io/rfc3339-iso8601/ #iso8601 #rfc3339 #standards

@amackif yes, agreed.

And I would also consider chrono as "broken/unfitting/lacking". The jiff docs explain why much better than I could.

I think as it comes to date and time handling, the reason isn't lack of interest but the huge complexity of time zones, daylight saving time shifts, and leap periods.

I admire the teams behind RFC 9557, Temporal as well as BurntSushi for taking this on.

#RustLang #JavaScript #RFC9557 #RFC3339 #Temporal

@foss_events may I suggest #RFC3339 for #date formatting to avoid confusion?

I actually dislike #ISO8601 and prefer #rfc3339.
e.g. because I can read the RFC free of charge while ISO8601 costs 18 CHF.
Another reason is https://ijmacd.github.io/rfc3339-iso8601/

So this is cool:

https://ijmacd.github.io/rfc3339-iso8601/

RFC 3339 is of course the best, since it supports date/time with space in between:

2024-12-12 16:03:17

#RFC3339 #ISO8601

Periodic reminder that according to #RFC #RFC3339 , if it's not YYYY-MM-DD you don't have a #date, you're just hanging out.
Also you want #RFC3339 and *not* #ISO8601, see https://ijmacd.github.io/rfc3339-iso8601/ for horrors the latter allows, and that's besides the fact that you need to pay around 200 CHF to read the whole spec.

And on that note, I received some documents that use M_D_YYYY in their naming... 🤢

Why, Ubisoft? Why?

#ISO8601 #RFC3339

An Ubisoft Connect prompt asking for your age as DD/MM/YYYY. If you enter a child's age, an email is sent to the parent asking them to get the child's account set up.

The follow-up prompt from the parent's perspective when setting up an Ubisoft Connect account for a child. You are asked to enter the child's date of birth, to confirm that it matches with what was entered by the child in the request. But while the initial prompt to the child is formatted as DD/MM/YYYY, this prompt is formatted as MM/DD/YYYY.

@Barredo That assumes local datetime is mostly useful. For me it's mostly not.

I want to be able to set date/time format separate from language. Usually English, sometimes another language I can speak. But I always want #iso8601 (or #rfc3339) date time notation. In windows I can set that easily. Not in browsers, on Linux, most M365 applications don't follow the datetime setting, just the language setting. Some do, some follow the location setting, meaning three different formats.

@fooderick
I used to say the same, but #RFC3339 is a much better idea. It does what you say, but does not allow for the horrible monsters that #ISO8601 does (`2024W046T10,9+0000` about takes the cake) - see https://ijmacd.github.io/rfc3339-iso8601/ for full comparison.
Also, being an ISO standard, you have to pay 173 CHF to be able to actually read it in full.

I always thought that #RFC3339 is a subset of #ISO8601, but apparently the former deviates from the latter. Something I discovered today when I was addressing a gap in the system.

Just check out this #cheatsheet that clearly shows what's common and what's not.

https://ijmacd.github.io/rfc3339-iso8601/

I just stumbled over this page about RFC3339 vs ISO 8601 timestamps. Nice way of showing the differences in a readable way.

https://ijmacd.github.io/rfc3339-iso8601/

#tech #RFC3339

@koakuma Realistically no one uses #ISO because they're rent-seeking assholes, people use #RFC #3339.

#RFC3339

TIL you can get dates and times formatted nicely in Firefox's Library window (Control+Shift+O) by setting intl.date_time.pattern_override.date_short to "yyyy-MM-dd", intl.date_time.pattern_override.time_short to "HH:mm", and intl.date_time.pattern_override.connector_short to "{1} {0}" in about:config or user.js.

Setting the LC_TIME environment variable to en_DK.UTF-8 does not work.

#firefox #rfc3339 #iso8601