@MochiEnjoyer@lemmy.dbzer0.com to 196@lemmy.blahaj.zone • 2 years agoMonthly rulelemmy.dbzer0.comimagemessage-square44fedilinkarrow-up1570arrow-down10
arrow-up1570arrow-down1imageMonthly rulelemmy.dbzer0.com@MochiEnjoyer@lemmy.dbzer0.com to 196@lemmy.blahaj.zone • 2 years agomessage-square44fedilink
minus-square@MystikIncarnate@lemmy.calinkfedilinkEnglish6•1 year agoYeah, we need some YYYY-MM-DDTHH:MM:SS-TZ All up in here. Gotta replace the last - with a + where applicable… Or just put a big old Z there instead… Optionally add some .### after the second too if you’re so inclined. Awww yeahhhhhh. I like that.
minus-square@apprehentice@lemmy.enchanted.sociallinkfedilink7•1 year agoI used to be pro-8601 until I learned the open standard that is RFC 3339
minus-squareDeebsterlinkfedilink3•edit-21 year ago¿Por qué no los dos? https://ijmacd.github.io/rfc3339-iso8601/
ISO 8601, represent!
YYYY-MM-DDTHH:MM:SS
Which timezone is this? B-, good effort
Yeah, we need some
YYYY-MM-DDTHH:MM:SS-TZ
All up in here. Gotta replace the last - with a + where applicable… Or just put a big old Z there instead… Optionally add some .### after the second too if you’re so inclined.
Awww yeahhhhhh. I like that.
I used to be pro-8601 until I learned the open standard that is RFC 3339
¿Por qué no los dos?
https://ijmacd.github.io/rfc3339-iso8601/