I think anyone who's been, uh, "in the shit" so to speak will understand that updating services that aren't even production ready means you have to take some precautions
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.
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.
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 looking forward to the UI changes also, as well as the switch to the HTTP API, but I'm really even more stoked about 0.18.1 (especially the CAPTCHA being redone) - which I feel like would be a better time to upgrade.
That said, it just came out today, so the admins will probably want to wait for stability's sake.
Admins are aware and are planning an upgrade. It's all volunteers juggling things of course, but there's active discussion going on. There are some potential changes to be reviewed. We should get updated soon^TM^
Add comment