this post was submitted on 03 Aug 2026
626 points (90.5% liked)
Lemmy Shitpost
41206 readers
3522 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
ISO 8601
ISO 8601
ISO week date
👆
RFC 3339 FTW!
Open source, and no ambiguous options grandfathered in.
Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise.
Though the way it specifies raw UTC times is odd (8601 uses
Z, 3339 uses-00:00), that got changed with RFC 9557 to align with 8601.It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g.
2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise.This is the only way to date.
No need for dashes
Except for, yknow, human readability
I've recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit.
Are a lots of things gonna break in about 8000 years?
As for why it's better:
ISO is better for archiving and sorting, inarguably so. But dd-mm-yyyy is better for day to day daily life usage, where the day and month are much more important than the year.
Both have their uses, but for different situations. mm-dd-yyyy is just batshit though.
Uh, no.
It literally just depends to what you are used to.
Yes, ISO-8601 is objectively better than YYYY/DD/MM or MM/DD/YYYY or other strange formats. But, because it isn't the most widely used format, it can be less efficient when there's no danger of MM/DD vs DD/MM confusion.
If person A is talking to person B and they're from the same culture, some culture-specific version like DD/MM/YY might be easier for them because it's what they're both used to, even if it is objectively inferior. But, if person A is talking to person C who is from a different place/culture things get more challenging because if the day of the month is 12 or under, it's hard to distinguish between DD/MM or MM/DD. Even if person C knows that person A comes from a place that does DD/MM, they don't know if person C used the native DD/MM format they're used to, or translated it to them to MM/DD because person A was trying to make things easy for person C.
One of the advantages of the hyphens in ISO-8601, aside from them working with files, is that hyphens in dates are less common than slashes, so if someone sees 1212-11-12 they're more likely to understand that it's an ISO-formatted date. If they see 1212/11/12 it might be a MM/DD date or a DD/MM date.
Start using it and suddenly it becomes most used. It is the little acts that make a difference.
To be fair, the time separators don't behave well on all implementations of filesystem access by filename. Need to use underscores or omit them at times.
And unlike most „forbidden characters“ for file names, the colon is actually used in NTFS: to separate the file path from the name of a ~~named fork~~ Alternate Data Stream.
See, I hadn't even read about this. TIL :)
Still, I use ISO8601 all the time when it comes to written dates :)
This is the way.
This is the way.
This is the (year-month-) day.
RFC 3339
ISO would be great, but sadly OmegaStar doesn't support ISO timestamps yet.
Wtf is an omega star?
The last star of the Greek alphabet? 🤷🏻
"While Galactus has omniscient knowledge of all current user data providers, it doesn't have future sight"
Just use EKS to deliver the feature this quarter, and block the OmegaStar migration on "the team gets their shit together" and supports ISO timestamps.
Except I can't get behind the time part of it, personally. I can see the point of doing GMT with the offset if you're working across multiple timezones, but it's overkill for situations where you aren't.
There's no way to predict how a date will be used. No reason not to be flexible. No reason to break convention.
That’s how my brother missed a train: the linux planner used GMT while the local train company planner used assumed local time…
So I disagree
I think we should all, as a globe, just pick one time zone and use that. I don't care if my 1:00 pm is the middle of that night. Everyone's 5:00pm will be 5:00pm. We will learn how to adjust our schedules for the master time zone.