this post was submitted on 03 Aug 2026
659 points (90.7% liked)

Lemmy Shitpost

41329 readers
3582 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/ExplicitContent


-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

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

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
 
top 50 comments
sorted by: hot top controversial new old
[–] BilboBargains@lemmy.world 6 points 6 days ago

ISO datetime, let's goooooo YYYYMMDDHHmmSS

[–] Willie169@infosec.pub 1 points 5 days ago

ISO-8601 or RFC-3339 is the way. It's not about which is better, but about that it would be confusing to use MMDDYYYY or DDMMYYYY since the other exists.

[–] FreshParsnip@lemmy.ca 2 points 6 days ago

Month first is better because when someone says the date aloud, they start with the month "August 5th, 2026"

[–] red_tomato@lemmy.world 319 points 1 week ago (45 children)
[–] 7EP6vuI@feddit.org 199 points 1 week ago (8 children)
[–] jlow@slrpnk.net 46 points 1 week ago
[–] GreyEyedGhost@piefed.ca 16 points 1 week ago (2 children)

RFC 3339 FTW!

Open source, and no ambiguous options grandfathered in.

load more comments (2 replies)
[–] plasma8726@lemmy.today 13 points 1 week ago

This is the only way to date.

load more comments (5 replies)
[–] merc@sh.itjust.works 63 points 1 week ago (9 children)

As for why it's better:

  1. It's in sort order. Even if you use it for things that don't understand dates, they sort properly because the day is the last part, month is the middle part, and year is the first part. If you include hours, minutes or seconds, the sort order is still preserved.
  2. Speaking of things that don't understand dates, because there are no slashes, you can easily use it in file names, directories, and anything else that treats slash as a special character. In addition, if you include the time part, because it uses "T" to separate the date and time, it doesn't use a space, so once again it can be easily used anywhere where a space might cause issues.
load more comments (9 replies)
[–] TootSweet@lemmy.world 28 points 1 week ago (2 children)
load more comments (2 replies)
[–] trem@lemmy.blahaj.zone 15 points 1 week ago
[–] mkwt@lemmy.world 13 points 1 week ago (2 children)
[–] TrickDacy@lemmy.world 13 points 1 week ago (4 children)
load more comments (4 replies)
load more comments (1 replies)
load more comments (40 replies)
[–] gandalf_der_13te@feddit.org 124 points 1 week ago (8 children)
[–] Adulated_Aspersion@lemmy.world 37 points 1 week ago (4 children)
[–] Mavenbushlog@lemmy.world 12 points 1 week ago

Long live the 8601

load more comments (3 replies)
[–] OddMinus1@sh.itjust.works 15 points 1 week ago

Yep. Doing that joke and landing on anything but ISO-8601 would be a huge red flag for me.

[–] Wirlocke@lemmy.blahaj.zone 15 points 1 week ago

Being able to sort numerically and have it also be in chronological order is sooo cool.

load more comments (5 replies)
[–] thingsiplay@lemmy.ml 90 points 1 week ago (6 children)
[–] Zink@programming.dev 12 points 1 week ago (3 children)

Yep and it needs to use hyphens and not slashes. It helps avoid missed typos or mis-reads in some situations, especially if hand-written.

[–] froufox@lemmy.blahaj.zone 14 points 1 week ago (1 children)

and it's perfectly sortable

load more comments (1 replies)
load more comments (2 replies)
load more comments (5 replies)
[–] Zikeji@programming.dev 80 points 1 week ago (1 children)

I read this meme and was physically revolted and wanted to immediately down vote. Great job.

The superior date format is, of course, ISO 8601. YYYY-MM-DD.

[–] dan@upvote.au 25 points 1 week ago* (last edited 1 week ago) (1 children)

RFC3339 is better than ISO8601 since it doesn't allow some of the esoteric formats, and allows some useful formats that ISO8601 doesn't (like separating date and time by a space instead of by T)

For example, 2026-W32-1 is also a valid ISO8601 date: Monday on the 32nd week of 2026. That format isn't allowed with RFC3339.

https://ijmacd.github.io/rfc3339-iso8601/

load more comments (1 replies)
[–] gex@lemmy.world 69 points 1 week ago* (last edited 1 week ago) (4 children)

yyyy/mm/dd, it's less ambiguous and it sorts nicely

Edit: so many replies suggesting using a hyphen as a separator, I'd like to compromise by using the oblique angle sign (⦧) which looks like a slash that becomes a hyphen in the middle. yyyy⦧mm⦧dd

[–] Pudutr0n@lemmy.world 15 points 1 week ago (4 children)
load more comments (4 replies)
[–] Carl@anarchist.nexus 12 points 1 week ago

Beat me to it, except I’d do yyyy-mm-dd because some OSes throw fits about having slashes in file names. Way better than the “Group Project-final FINAL v3 PAUL USE THIS ONE.file” versioning system that people seem to use.

load more comments (2 replies)
[–] LordKitsuna@lemmy.world 54 points 1 week ago
[–] AnnaFrankfurter@lemmy.ml 36 points 1 week ago

ISO 8601 or gtfo

[–] Duamerthrax@lemmy.world 35 points 1 week ago (1 children)
load more comments (1 replies)
[–] Xyphius@lemmy.ca 27 points 1 week ago (5 children)

I feel like DD/MM/YYYY is the same as doing: ss:mm:HH and I find that confusing.

load more comments (5 replies)
[–] dEVbiKub@feddit.nu 24 points 1 week ago (1 children)

That's a red flag... He has obviously not received the xkcd PSA.

load more comments (1 replies)
[–] Iusedtobeanalien@lemmy.world 24 points 1 week ago (2 children)
[–] craftrabbit@lemmy.zip 17 points 1 week ago (2 children)

Please use any kind of separation character or I'm gonna lose my mind

[–] Appoxo@lemmy.dbzer0.com 12 points 1 week ago (3 children)

Best I can give you is a single "_"

load more comments (3 replies)
load more comments (1 replies)
load more comments (1 replies)
[–] procrastitron@lemmy.world 18 points 1 week ago (2 children)

Anyone who wants to write the millennium between the month and century loses all credibility when arguing about date formats.

YYYY-MM-DD is the only coherent date format.

load more comments (2 replies)
[–] M137@lemmy.today 16 points 1 week ago (9 children)

ITT: people saying one thing is better than any other without thinking of context.
If I want to know today's date ISO 8601 isn't a good answer. And if I put stuff in folders by date then DD-MM-YYYY is a real bad way to do it. But MM-DD-YYYY is the worst one no matter the context.

[–] KernelTale@programming.dev 27 points 1 week ago

I like YYYY-MM-DD because then I don't have to figure out half the time if they used MM-DD-YYYY or if they were sane.

load more comments (8 replies)
[–] sik0fewl@piefed.ca 15 points 1 week ago (4 children)

I proper shit post would have suggested “mm/dd/yyyy”.

load more comments (4 replies)
[–] abc@suppo.fi 14 points 1 week ago

The one that ends us with f... I mean ISO 8601 of course

[–] drath@lemmy.drath.ru 14 points 1 week ago (1 children)

Months are stupid anyway, lets drop them and swap for what they were supposed to represent instead: the moon phase, so today would be 216-2026-Waning Gibbous

load more comments (1 replies)
[–] chickenf622@sh.itjust.works 13 points 1 week ago* (last edited 1 week ago) (3 children)

~~ISO 8601~~ RFC 3339 (yyyy-mm-dd) for storing dates in software. Any format that that goes in the order of day, month, and year for conversational/presentational purposes, preferable the format is dynamic depending on the user's locale (even for those that want the month first). There now everyone is happy.

Edit: switched to RFC 3339 since it is a subset of ISO 8601 that is more strict, and I love semantics.

load more comments (3 replies)
[–] dlsloop@lemmy.zip 13 points 1 week ago (2 children)

I'm a YYYY/MM/DD man myself

load more comments (2 replies)
[–] Grostleton@lemmy.dbzer0.com 13 points 1 week ago (2 children)

I prefer ddd/yyyy, much simpler

[–] fartsparkles@lemmy.world 23 points 1 week ago* (last edited 1 week ago) (1 children)

Ah yes, Mon/2026, perfect…

load more comments (1 replies)
load more comments (1 replies)
[–] whotookkarl@lemmy.dbzer0.com 11 points 1 week ago (1 children)

1785793853 seconds since Linux epoch

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