Deegham@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 2 年前measuring rulelemmy.blahaj.zoneimagemessage-square279fedilinkarrow-up11.39Karrow-down10
arrow-up11.39Karrow-down1imagemeasuring rulelemmy.blahaj.zoneDeegham@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 2 年前message-square279fedilink
minus-squarefilcuk@lemmy.ziplinkfedilinkarrow-up7·2 年前In case people need a nudge to convert: https://ijmacd.github.io/rfc3339-iso8601/
minus-squarebort@feddit.delinkfedilinkarrow-up3·2 年前tbh 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·2 年前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.
minus-squareitslilith@lemmy.blahaj.zonelinkfedilinkarrow-up2·2 年前I think you’re right, but also windows file system is a dumpster fire
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
deleted by creator
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