It's the only way.
this post was submitted on 01 May 2025
1079 points (97.0% liked)
Comic Strips
16328 readers
1535 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- !linuxmemes@lemmy.world: "I use Arch btw"
- !memes@lemmy.world: memes (you don't say!)
founded 2 years ago
MODERATORS
I feel like YYYYMMDD (without dashes) might be a format in ISO 8601, but I'm fully expecting to be corrected soon. But I didn't say think, I said feel. YYYYMMDD has a similar vibe to YYYY-MM-DD, ya feel me?
Nope, you are correct! From the Wikipedia page, which cites the standards document:
- Representations can be done in one of two formats – a basic format with a minimal number of separators or an extended formatwith separators added to enhance human readability. The standard notes that "The basic format should be avoided in plain text." The separator used between date values (year, month, week, and day) is the hyphen, while the colon is used as the separator between time values (hours, minutes, and seconds). For example, the 6th day of the 1st month of the year 2009 may be written as "2009-01-06" in the extended format or as "20090106" in the basic format without ambiguity.
load more comments
(1 replies)
load more comments
(1 replies)
I work at a global company an in my team there are people from 5 continents. we use 27-Feb-23. It's the only way nobody gets confused and it's only 1 char more. (Tbf nobody would be confused only my boss that is american lol)
load more comments
(7 replies)
RFC-3336
I figured there were problems with existing calendars, so I created a new one to supersede all others. That reminds me, though: I need to declare the "official" format for the calendar, to avoid all this nonsense.
I see a window of opportunity, here. Normally, there's no chance for any calendar revision to succeed in adoption; however, I think if I use the right words with the President, I could get it pushed into adoption by fiat. Y'all had best start learning my new calendar to get ahead of everyone else.
Note for the humorously disadvantaged: the Saturnalia Calendar is a mechanism through which I'm playing with a new (to me) programming language. I am under no disillusion that anyone else will see the obvious advantages and clear superiority of the Saturnalia Calendar, much less adopt it. And no comments from the peanut gallery about the name! What, did you expect me to actually spend time thinking of a catchy name when a perfectly good, mostly unused one already existed?
load more comments
(11 replies)
I regularly work with Americans, Canadians, and Europeans. So many times each group defaults to their own format and mistakes occur I gave up on all the formats listed by OP. If i have to write a date in correspondence its like: Feb 27th 2013. No ambiguity. No one has ever challenged me on it either. It is universally understood.
load more comments
(34 replies)