this post was submitted on 03 Aug 2026
236 points (91.3% liked)
Lemmy Shitpost
41152 readers
3798 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
As for why it's better:
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.
💯
ISO 8601
👆
This is the way.
This is the way.
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? 🤷🏻
RFC 3339
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
Yeah, the time part should obviously be written in Swatch Internet Time, he writes at @910.
How so, out of curiosity?
If you work at a company where all of its offices are in the same time zone and you're time-stamping logs, then it's more expedient for understanding and placing an event in time against other things to use local time.
Unless everything is already standardized as GMT with offset I guess, but I feel like down that route lies madness.
"I got your email at 20:37:45-7:00" is a few more steps than "I got your email at 1:37PM".
It's not a big hurdle, but I try to design for the newest member on the team scrambling in panic rather than a calm cool professional already familiar with conventions.
Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more "workable" compromise.
It’s great, and standard for software. But do any of y’all communicate dates like this in your personal life?
Like “want to go to a hockey game with me 2026-10-17?” As cursed as mm-dd-yy is, it feels a lot more natural in conversation.
Say when is that independence day of yours?
There is nothing 'natural' about mm/dd/yy, it is just what you are used to - end of story.
What you are used to inevitably becomes more natural for you subjectively...
I knew I would eat shit for that comment.
July 4th is a funny example cause you can say “the 4th” and everyone knows what you mean, but people also say “4th of July” to give it more importance.
That’s a lot less common for other dates, Americans aren’t commonly saying “25th of December”.
I absolutely full out dates in iso 8601 any time I'm required to sign a form.
I like your style. I'll start doing that, (unless a format is specified, because I'm no protocol breaker.)
dd-mm feels completely natural to say in conversation. “Do you want to go to a X with me on the 3rd of August”
Does "August 3rd" sound unnatural to you?
In spoken conversation it doesn't really matter. In many contexts you could probably just say "Want to go on the third?" and the person you're talking to will understand you mean August the third of this current year.
It does to me. mm-dd is not used at all in my native language and would be considered grammatically incorrect. Since English doesn't prescribe it I have no reason to fully accept it.
Note that I still prefer to write ISO 8601 dates but my spoken dates are big-endian.
Middle-endian dates like "June 15th 2046" are just bad, of course.
I commented earlier that having to say more words is inefficient, but what yiu said made me think... In other languages I know, it's basically spoken as "3rd August'... Eliminating the inefficiency. It's really more English's general inefficiency that irks me, more so than the order of the dates lol
But... what YEAR!?!?
Its fine but its unnecessarily long. Its just one syllable/word but its extra.
Two words when used in a sentence. "The 3rd of August" vs "August 3rd"
There's no reason the two need to be the same. We don't talk in heximal either
Yes (I'm insane)
Yes as well (Also insane) but its universally ledgable, sorts on computers easier, accomodates timezones and sub-second units. ISO-8601 should be the universal standard, and anyone who says otherwise better show up with a white paper explaining why. None of this dumb american format or javascript web form bullshit, language is about specificity, BE SPECIFIC. Unless you want to go off the rails and talk about relativity, time dialation and reference points... But thats all above my pay grade. ISO-8601 is a golden example of "good enough for normal people". Thank you for coming to my TEDtalk.
Yes, kind of.
I shorthand it verbally unless I'm giving a full date, but typed, it's almost always yyyy-MM-dd HH:mm:ss (whichever part of that is relevant).
I do this because I believe it's the most logical, it sorts properly without having to use a datetime library, and it can't be confused with another system (is 12-1-2026 in the future or the past? No way to know just by looking at it).
Just shortening it to MM-dd could cause confusion with anyone not in the US so I'll typically include the year as well (also useful if I wind up having to look at old notes or emails to not have to figure out the year I meant ... Which has happened more than once ...)
Only a truly insane person would use mm-dd-yy in conversation. “Want to go to a hockey game with me ten seventeen twenty-six?” Or worse, “…oh four oh seven twenty-seven.” Pure madness.
Conversationally, mmm d yy or d mmm yy (usually just shortened to mmm d or d mmm) is where it’s at.