Bob to Lemmy ShitpostEnglish • 7 months agoEveryday, as an Americanmidwest.socialimagemessage-square322fedilinkarrow-up11.31Karrow-down146
arrow-up11.26Karrow-down1imageEveryday, as an Americanmidwest.socialBob to Lemmy ShitpostEnglish • 7 months agomessage-square322fedilink
minus-square@[email protected]linkfedilink3•7 months agoSome ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-square@[email protected]linkfedilinkEnglish6•7 months agoThe ones without separators tend to be for server/client exchange though.
minus-square@[email protected]linkfedilink2•7 months agoI agree but they’re hard to read at a glance when debugging and there’s lots of them :) Having said that, a lot of client-server communications use Unix timestamps though, which are even harder to read at a glance.
minus-square@[email protected]linkfedilinkEnglish1•edit-27 months agoAt least it’s human readable and not protobuf 😬 * though the transport channel doesn’t really matter it could be formatted this way anyhow.
Some ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
The ones without separators tend to be for server/client exchange though.
I agree but they’re hard to read at a glance when debugging and there’s lots of them :)
Having said that, a lot of client-server communications use Unix timestamps though, which are even harder to read at a glance.
At least it’s human readable and not protobuf 😬 * though the transport channel doesn’t really matter it could be formatted this way anyhow.
I mean I like this one without the separations