• dan@upvote.au
    link
    fedilink
    arrow-up
    3
    ·
    7 months ago

    Some ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).

    • zqwzzle@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 months ago

      The ones without separators tend to be for server/client exchange though.

      • dan@upvote.au
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        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.

        • zqwzzle@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          7 months ago

          At least it’s human readable and not protobuf 😬 * though the transport channel doesn’t really matter it could be formatted this way anyhow.