MochiEnjoyer@lemmy.dbzer0.com to 196@lemmy.blahaj.zone · 1 year agoMonthly rulelemmy.dbzer0.comimagemessage-square50fedilinkarrow-up1577arrow-down11
arrow-up1576arrow-down1imageMonthly rulelemmy.dbzer0.comMochiEnjoyer@lemmy.dbzer0.com to 196@lemmy.blahaj.zone · 1 year agomessage-square50fedilink
minus-squareQwaffle_waffle@sh.itjust.workslinkfedilinkarrow-up50arrow-down1·1 year agoISO 8601, represent!
minus-squareDeebster@lemmy.mllinkfedilinkarrow-up10·1 year agoWhich timezone is this? B-, good effort
minus-squareMystikIncarnate@lemmy.calinkfedilinkEnglisharrow-up7·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-squareapprehentice@lemmy.enchanted.sociallinkfedilinkarrow-up7·1 year agoI used to be pro-8601 until I learned the open standard that is RFC 3339
minus-squareDeebster@lemmy.mllinkfedilinkarrow-up3·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/