this post was submitted on 23 Jun 2023
23 points (100.0% liked)

Beehaw Support

2796 readers
2 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.


if you can see this, it's up  

founded 2 years ago
MODERATORS
 

Would be great to get upgraded soon! Lots of UI improvements.

you are viewing a single comment's thread
view the rest of the comments
[–] NekoRogue@beehaw.org 17 points 1 year ago (2 children)

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.

[–] Penguincoder@beehaw.org 9 points 1 year ago

Beehaw has not updated to the newest version of Lemmy yet. Might be an issue with Jerboa, or just a coincidence error.

[–] Rentlar@beehaw.org 8 points 1 year ago (2 children)

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.

[–] nickb333@beehaw.org 5 points 1 year ago

Same issue here. I won't pretend to understand the reasons behind it, only panic because I saw the error 😔 pop-up.

[–] NekoRogue@beehaw.org 2 points 1 year ago

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.