Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 6 months agoEveryday, as an Americanmidwest.socialimagemessage-square323fedilinkarrow-up11.31Karrow-down146
arrow-up11.26Karrow-down1imageEveryday, as an Americanmidwest.socialBob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 6 months agomessage-square323fedilink
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up6·6 months agoThe ones without separators tend to be for server/client exchange though.
minus-squaredanAlinkfedilinkarrow-up2·6 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-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up1·edit-26 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.
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.