There’s a server error (likely a HTTP 500). Jerboa can’t correctly handle them.
this is the correct answer. usually because the server middleware is unable to complete a request due to overload or some other issue. issues like these will get better over time as things are refined. just hang tight.
From what I can tell this is generally a timeout error on your Lemmy instance’s part.
Essentially the error is saying that instead of the expected JSON of posts or comments, it got a string (typically an error code)
It’s an internal error that is shown to you. I’ve seen this before when you leave some text in the reply text box and then press back.
I need to check whether this has been reported as an issue.
I’m interested in fixing stuff like this, but my instance is frustratingly stable.
It generally means your server is overloaded.
There is a high chance that the server is returning a 500 error which means the server application has failed to handle your request. Most likely your instance is overloaded.
Unfortunately the Jerboa code doesn’t currently handle different login errors very well.
