this post was submitted on 11 Jun 2025
443 points (86.5% liked)
memes
15487 readers
1 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
After all the self-important blowhards in the committe were satisified that they had put their fingerprint on the ISO8601 document with bullshit like "year-month-week" format support and signed off, they went home.
The rest stayed behind, waited a few minutes to be safe, and then quickly made RFC3339 like a proper standard.
This is what RFC3339 vs ISO8601 feels like.
Let's not forget that technically you have to pay for ISO8601, despite it being nearly useless as a standard because it allows several incompatible formats to coexist.
Fucking wild.
While a fucking stupid concept, it's nice that this particular format has a monetary deterrent.
Only if you want to say you have the certification for it, you can use it if you want, that is fine
ISO8601 is YYYY-MM-DD nothing to do with weeks and isn;t the only difference of RFC3339 that you can use a space instead of a T in between the date and time? Also RFC3339 is only an internet standard while ISO is a generally international standard?