this post was submitted on 26 Jan 2025
603 points (96.0% liked)

196

16837 readers
1143 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago
MODERATORS
603
ISO 8601 ftw rule (gregtech.eu)
submitted 3 days ago* (last edited 3 days ago) by [email protected] to c/[email protected]
 

[email protected] gang, rise up

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 day ago

Y'all be riskin it without holocene crypty

SYSM:YY.DM.TzYDY.H.H

4:40.42p EST on Jan 28, 12,025 ->

  • 4120:20.21.-4285.1.6

That's the one that was active when I started typing. However, I change it randomly using the decay of a radioactive isotope that is randomly chosen by the decay of a separate amount of Uranium-238. I'm two randoms in. This way, my time records are always encrypted using open-science source and the government can't hack the pictures of my parking spots at the oncology center to sell them to the NIMBYs at MetAlphabet AI.

[–] [email protected] 16 points 2 days ago

I use ss/mm/hh/dd/MM/YYYY

t.european

[–] [email protected] 3 points 2 days ago* (last edited 2 days ago)

I just use millis since epoch

(Recently learned that this isn't accurate because it disguises leap seconds. The standard was fucked from the start)

[–] [email protected] 88 points 3 days ago (2 children)

"Europe", as if there weren't several languages in Europe with different date formats per language...

[–] [email protected] 86 points 3 days ago (18 children)

None of which start with the month because that would be fuckin stupid

load more comments (18 replies)
[–] [email protected] 1 points 2 days ago

Keep that kinda talk up and you'll go straight to tariff!

[–] [email protected] 52 points 3 days ago (1 children)

I work with international clients and use 2025-01-26 format. Without it.. confusion.

[–] [email protected] 31 points 3 days ago

That's an ISO date, and it's gorgeous. It's the only way I'll accept working with dates and timezones, though I'll make am exception for end-user facing output, and format it according to locale if I'm positive they're not going to feed into some other app.

[–] [email protected] 101 points 3 days ago

MM ≠ MM !!!

[–] [email protected] 20 points 3 days ago

finally a correct version of this diagram

[–] [email protected] 2 points 2 days ago

This is the way.

[–] [email protected] 55 points 3 days ago (11 children)

This pyramid visualisation doesn't work for me, unless you read time starting with seconds.

[–] [email protected] 29 points 3 days ago (2 children)

A pyramid is built bottom to top, not top to bottom. That's also one of the strengths of the ISO format. You can add/remove layers for arbitrary granularity and still have a valid date.

[–] [email protected] 28 points 3 days ago

Yeah, but people read top to bottom. The best way to do it would be to have upside down pyramids. With the biggest blocks at the top representing the biggest unit of time (YYYY) and the smallest blocks at the bottom representing seconds & smaller.

load more comments (1 replies)
load more comments (10 replies)
[–] [email protected] 32 points 3 days ago (14 children)

I don't know why anyone would ever argue against this. Least precise to most precise. Like every other number we use.

(I don't know if this is true for EVERY numerical measure, but I'm sure someone will let me know of one that doesn't)

load more comments (14 replies)
[–] [email protected] 34 points 3 days ago (2 children)

I'm almost 40 and now just realizing my insistence on how to structure all my folders and notes is actually an ISO standard. Way to go me.

load more comments (2 replies)
[–] [email protected] 21 points 3 days ago (1 children)

All my homies hate ISO, RFC 3339 for the win.

[–] [email protected] 20 points 3 days ago* (last edited 3 days ago) (2 children)

All my homies hate ISO

Said no-one ever?

EDIT: thanks for informing me i now retract my position

[–] [email protected] 36 points 3 days ago (7 children)

Nah, ISO is a shit organization. The biggest issue is that all of their "standards" are blocked behind paywalls and can't be shared. This creates problems for open source projects that want to implement it because it inherently limits how many people are actually able to look at the standard. Compare to RFC, which always has been free. And not only that, it also has most of the standards that the internet is built upon (like HTTP and TCP, just to name a few).

Besides that, they happily looked away when members were openly taking bribes from Microsoft during the standardization of OOXML.

In any case, ISO-8601 is a garbage standard. P1Y is a valid ISO-8601 string. Good luck figuring out what that means. Here's a more comprehensive page demonstrating just how stupid ISO-8601 is: https://github.com/IJMacD/rfc3339-iso8601

load more comments (7 replies)
[–] [email protected] 12 points 3 days ago (1 children)

if i am not wrong, it is because essentially both are same (slight differences in what is allowed and what is not, https://github.com/IJMacD/rfc3339-iso8601), but RFC is more free as in freedom

load more comments (1 replies)
[–] [email protected] 27 points 3 days ago (2 children)

YYYY.MM.DD HH.MM.SS, as eru ilúvatar intended

[–] [email protected] 3 points 2 days ago

YYYY-MM-DD HH:MM:SS

Ftfy

load more comments (1 replies)
[–] [email protected] 25 points 3 days ago

My stupid ass read this top to bottom and I was confused why anyone would start with seconds

[–] [email protected] 16 points 3 days ago (1 children)

I know, why don't we all agree to agree and use every single possible format within a shared spreadsheet

load more comments (1 replies)
[–] [email protected] 13 points 3 days ago (5 children)

Mmm US military date and time is fun too.

DDMMMYYYYHHMM and time zone identifier. So 26JAN20251841Z.

So much fun.

load more comments (5 replies)
load more comments
view more: next ›