MochiEnjoyer@lemmy.dbzer0.com to 196@lemmy.blahaj.zone · 2 years agoMonthly rulelemmy.dbzer0.comimagemessage-square46fedilinkarrow-up1582arrow-down11
arrow-up1581arrow-down1imageMonthly rulelemmy.dbzer0.comMochiEnjoyer@lemmy.dbzer0.com to 196@lemmy.blahaj.zone · 2 years agomessage-square46fedilink
minus-squareDeebster@lemmy.mllinkfedilinkarrow-up10·2 years agoWhich timezone is this? B-, good effort
minus-squareMystikIncarnate@lemmy.calinkfedilinkEnglisharrow-up7·2 years 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-squareapprehentice@lemmy.enchanted.sociallinkfedilinkarrow-up7·2 years agoI used to be pro-8601 until I learned the open standard that is RFC 3339
minus-squareDeebster@lemmy.mllinkfedilinkarrow-up3·edit-22 years 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/