Bob to Lemmy [email protected]English • 27 days agoEveryday, as an Americanmidwest.socialimagemessage-square323fedilinkarrow-up11.31Karrow-down146
arrow-up11.26Karrow-down1imageEveryday, as an Americanmidwest.socialBob to Lemmy [email protected]English • 27 days agomessage-square323fedilink
minus-square@[email protected]linkfedilinkEnglish5•26 days agoThe ones without separators tend to be for server/client exchange though.
minus-square@[email protected]linkfedilink2•26 days 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-225 days 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.