this post was submitted on 12 Dec 2023
629 points (95.1% liked)

Memes

45223 readers
1514 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
629
Standards shouldn't be behind a paywall (lemmy.world)
submitted 9 months ago by [email protected] to c/[email protected]
102 comments fedilink hide all child comments
 
  • ISO 8601 is paywalled
  • RFC allows a space instead of a T (e.g. 2020-12-09 16:09:...) which is nicer to read.
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 9 months ago (2 children)

This is about the old argument around how date strings are formatted.

MMDDYYYY vs YYYYMMDD, spaces or hyphens may differ. It's an old and passionate argument (mostly due to the American approach of starting with the month being insane)

[–] [email protected] 21 points 9 months ago (2 children)

Both ISO8601 and RFC3339 are YYYY-MM-DD. The difference is in how the date and time are separated.

[–] [email protected] 7 points 9 months ago

Than you! I was shooting from the hip half asleep (the classic 'gosh I'm so clever' moment for me...)

[–] [email protected] 2 points 9 months ago

Also, ISO 8601 has some handy rules for expressing time lengths and periodicities.

[–] [email protected] 6 points 9 months ago (1 children)

I've worked with this one project for so long I can now read +%s timestamps.

[–] [email protected] 1 points 9 months ago

That's a certain kind of skill I wouldn't want the need to have. I just copy paste those timestamps into a terminal with date -d @ (and always forget the right syntax for that :D)