• Serinus@lemmy.ml
    link
    fedilink
    English
    arrow-up
    19
    ·
    2 years ago

    I think it’s both, actually. Lemmy is often giving html where json is expected, and Jerboa isn’t handling the error well.

    • usernotfound@lemmy.ml
      link
      fedilink
      English
      arrow-up
      20
      ·
      2 years ago

      🤔 The server spits out html when it cannot reach the backend. So one could argue it’s a configuration issue because the admin didn’t provide enough capacity / didn’t set up a proper generic json error for backend failures.

      FWIW, Liftoff doesn’t handle these super gracefully either.

      At any rate I think it’s kinda awesome that we get to witness these kinds of infancy problems.

      • entropicdrift
        link
        fedilink
        English
        arrow-up
        23
        ·
        2 years ago

        It should display a human-readable error message instead of the raw one.

      • Atemu@lemmy.ml
        link
        fedilink
        English
        arrow-up
        18
        ·
        2 years ago

        Take it as an error, tell the user about it and then retry with exponential back-off.