Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 4 months agoEveryday, as an Americanmidwest.socialimagemessage-square81fedilinkarrow-up115arrow-down11
arrow-up114arrow-down1imageEveryday, as an Americanmidwest.socialBob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 4 months agomessage-square81fedilink
minus-squareJo Miran@lemmy.mllinkfedilinkarrow-up4·4 months agoWhile we are at it, let’s all (as in the entire planet) switch to 24hour UTC and the YYYY.MM.DD date format.
minus-squaredan@upvote.aulinkfedilinkarrow-up0·4 months agoSome ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up1·4 months agoThe ones without separators tend to be for server/client exchange though.
minus-squareShardikprime@lemmy.worldlinkfedilinkarrow-up0arrow-down1·4 months agoI mean I like this one without the separations
minus-squarecmhe@lemmy.worldlinkfedilinkarrow-up0·edit-24 months agoWhile we at that, lets switch to the international fixed calendar as well.
minus-squareamelore@slrpnk.netlinkfedilinkEnglisharrow-up1·4 months agoMove New Years back to march 1st, then the Latin roots will be accurate again.
While we are at it, let’s all (as in the entire planet) switch to 24hour UTC and the YYYY.MM.DD date format.
ISO8601 gang
Some ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
The ones without separators tend to be for server/client exchange though.
I mean I like this one without the separations
While we at that, lets switch to the international fixed calendar as well.
Move New Years back to march 1st, then the Latin roots will be accurate again.