I'm getting this on Jerboa after their latest update today, I'm guessing it's temporary while we're upgrading but just wanted to point it out in case it was helpful in some way.
Beehaw has not updated to the newest version of Lemmy yet. Might be an issue with Jerboa, or just a coincidence error.
So v.35 of Jerboa supports only Lemmy 0.18.x
versions v.34 of Lemmy and earlier support Lemmy 0.17.x and lower.
The websocket to HTTP change is kind of breaking. I find if you were already logged in the app before the server updated you can still post and stuff in the server. But you can't log in anymore.
Same issue here. I won't pretend to understand the reasons behind it, only panic because I saw the error 😔 pop-up.
That explains why I can still see Beehaw and post comments through Jerboa, I was already logged in. I'm getting a few little bugs though, but that's to be expected with a new platform so I'm not too worried about it. It's kinda fun watching a new platform get started.
I'm getting this on Jerboa after their latest update today, I'm guessing it's temporary while we're upgrading but just wanted to point it out in case it was helpful in some way.
Beehaw has not updated to the newest version of Lemmy yet. Might be an issue with Jerboa, or just a coincidence error.
So v.35 of Jerboa supports only Lemmy 0.18.x
versions v.34 of Lemmy and earlier support Lemmy 0.17.x and lower.
The websocket to HTTP change is kind of breaking. I find if you were already logged in the app before the server updated you can still post and stuff in the server. But you can't log in anymore.
Same issue here. I won't pretend to understand the reasons behind it, only panic because I saw the error 😔 pop-up.
That explains why I can still see Beehaw and post comments through Jerboa, I was already logged in. I'm getting a few little bugs though, but that's to be expected with a new platform so I'm not too worried about it. It's kinda fun watching a new platform get started.