Deegham@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 1 year agomeasuring rulelemmy.blahaj.zoneimagemessage-square243fedilinkarrow-up11.29Karrow-down10
arrow-up11.29Karrow-down1imagemeasuring rulelemmy.blahaj.zoneDeegham@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 1 year agomessage-square243fedilink
minus-squarefilcuk@lemmy.ziplinkfedilinkarrow-up6·1 year agoIn case people need a nudge to convert: https://ijmacd.github.io/rfc3339-iso8601/
minus-squarebort@feddit.delinkfedilinkarrow-up3·1 year agotbh they both have way too many options. just give me 2023-11-21T21:45:53.02Z and call it a day
minus-squarewookiestackhouse@lemmy.worldlinkfedilinkarrow-up1·1 year agoIs it just me or do neither ISO8601 nor RFC3339 contain any timestamp formats that are windows file system compliant? There doesn’t seem to be a time format that doesn’t contain a colon.
minus-squareitslilith@lemmy.blahaj.zonelinkfedilinkarrow-up2·1 year agoI think you’re right, but also windows file system is a dumpster fire
minus-squareperviouslyiner@lemm.eelinkfedilinkEnglisharrow-up1·1 year agonever noticed until now that they start at 1BC and call it 0000
meh, I prefer RFC 3339
In case people need a nudge to convert:
https://ijmacd.github.io/rfc3339-iso8601/
tbh they both have way too many options.
just give me 2023-11-21T21:45:53.02Z and call it a day
Damn, y’all are nerds.
what do you expect on lemmy
Is it just me or do neither ISO8601 nor RFC3339 contain any timestamp formats that are windows file system compliant? There doesn’t seem to be a time format that doesn’t contain a colon.
I think you’re right, but also windows file system is a dumpster fire
never noticed until now that they start at 1BC and call it 0000