Feb 27th 2013
Boom. Everything is in a different format so you can order it however you want and it's still readable.
this post was submitted on 01 May 2025
19 points (100.0% liked)
Comic Strips
17590 readers
1888 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
@m_f@discuss.online this might be applicable to the farside as well
Do you mean the post titles? I've been using the same format as was used since before I took over posting, but if people want ISO format that works for me
Everyone should use date-time groups so we're all on the same page down to the second.
DDHHMMSSZmmmYY
%Y%m%dT%H%M%SZ
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)
You can even save a character by using NATO dates (leaving out the useless hyphens): 01DEC1953
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?
load more comments
(1 replies)
There are several people in the comments saying they have to use 27 Feb 2013 because they work with people all over the world. I’m really confused - what does that solve that 2013-02-13 does not? I know that not every language spells months the English way so “Dec” or “May” aren’t universal. Is there some country that regularly puts year day month that would break using ISO 8601 or RFC 3339?
load more comments
(11 replies)
You know, I used to think ISO 8601 was just a boring technical standard for writing dates. But now I see it’s clearly the first step in a grand master plan! First, they make us write the year first, then the month, then the day-suddenly, our beloved 17.05.2025 turns into 2025-05-17. My birthday now looks like a WiFi password, and my calendar feels like a math equation.
But it doesn’t stop there. Today it’s the date format, tomorrow we’ll all be reading from right to left, and before you know it, our keyboards will be rearranged so QWERTY is replaced with mysterious squiggles and dots. Imagine the panic:
“First they came for our dates, then they came for our keyboards!”
At this rate, I’ll be drinking mint tea instead of coffee, my local kebab shop will start offering lutefisk shawarma, and Siri will only answer to “Inshallah.” The right-wing tabloids will have a field day:
“Western Civilization in Peril: Our Months and Days Held Hostage!”
But let’s be honest-if the worst thing that happens is we finally all agree on how to write today’s date, maybe world peace isn’t so far off. Until then, I’ll be over here, clutching my calendar and practicing my right-to-left reading skills… just in case.
(Don’t worry,this was just a joke! No offense intended-unless you’re a die-hard fan of confusing date formats, in which case, may the ISO be ever in your favor!)
Peace!
load more comments
(1 replies)
27.2.2013 is fine for handwriting on paper
For your example, maybe. If someone writes 8/3/2012, you don't know which is month/day. And if they shorten it to 08/03/12 you literally can't even conclusively determine the year, much less the month or day...
8/3/2012
You do. 8th of Feb in the entire civilised world and possibly 3rd of something in Trumpistan.
The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn't happen that way though...
The BEST way is to use the number of seconds after the J2000 epoch (The Gregorian date January 1, 2000, at 12:00 Terrestrial Time)
ISO 8601 goes from 1582 (Julian calendar adoption) but can go even further with agreement about intention and goes down beyond the millisecond. Not sure why I want an integer from the year 2000 which only represents seconds.
load more comments
(1 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?
Hey, I quite like this! You're the first person I've found that's thought of fixing the calendar by adopting six-day weeks. I have a very similar personal version, with two main differences:
- there's a leap week instead of a leap day, that way weekdays are always the same without having to skip any and every year has a whole number of weeks (either 61 most years [roughly 7 out of every 8] or 60 on short years [roughly 1 out of every 8])
- December includes this leap week and it's either 30 or 36 days long, depending on the year. I put it at the end of December for the same logic that you put Saturnalia at the end of the year, to not mess with cardinal dates and so that the Xth day of the year is always the same date
I also came to the same conclusion about workweeks. With two-day weekends, the Gregorian calendar has 71 % of workdays but the new calendar only has 67 %. On a thirty-day month this means 20 workdays instead of 21,5. Having the six-day week could also theoretically allow for a move to three- or two-day weeks in a post-scarcity future and doing away with weekends, as well has having either 50 % or 67 % of the workforce being active every day of the week, and not the wild levels of fluctuation seen today. Not having 100 % commuting some days of the week and a fraction of that on others would allow to scale things like transport infrastructure much more effectively
How does that work, with the leap week? Doesn't the year drift out of alignment with the solar cycle?
Only in eight year chunks. By year seven there is more unalignment than there was in year one, but it goes back to normal on year eight. Same thing as with leap days, just a slightly bigger scale.
In fact, with current rules, the shift in the regular Gregorian calendar becomes quite big when considering 100-year and 400-year cycles. In theory, a leap week calendar with new and updated rules could have a very comparable if not a smaller average deviation from the true solar date, though I haven't ran the precise calculations
load more comments
(3 replies)
Until microsoft makes that the default down in the lower right corner, I don't think we'll make much headway. I've been trying to get my office to do their dated files in YYYYMMDDHHMM for years. I do mine that way but I can't get anybody else to comply. This meme lists that as a discouraged format, I guess the dashes are ISO but I don't care about the dashes. I would accept doing YYYY-MM-DD over MMDDYYYY any time though.