I recently noticed my app (liftoff) stopped working and also glitchy behavior from the site after the sudden upgrade to 0.19, is there any explanation or reason for the sudden upgrade, especially considering that 0.19 isn’t exactly production ready (no official release from the devs).
Yes, an explanation would be great, @sdf@user224@lemmy.sdf.org
Huh. I’m not sure why that happened. I tried sdf@lemmy.sdf.org I thought. It autocompleted somehow.
Jerboa is broken as well. Can’t log in at all.
Eternity works, FWIW.
On a semi-related note, has anyone managed to use the new instance-block feature in Settings > Blocks? When I try to search for an instance to block, it just displays a short random-looking list of instances, which never changes, and I can’t block anything not in that list. Tried in multiple browsers on multiple systems.
Eternity “works” in that I can see posts and comments, but I can’t upvote or comment myself. (The error I get is “Code 401 Body: null”.)
Lemmy 0.19 Breaking Changes
Lemmy 0.19.0-rc.4 and Development Update - 2023-11-03
We are also readying another release candidate
0.19.0-rc.4. As usual it is available for testing on voyager.lemmy.ml and by installing the Docker image on your server. There are no breaking changes this time as we are preparing for the final release. It has been one month since we announced the major breaking changes for 0.19. In that sense we would like to know from developers of Lemmy clients and frontends if their projects are ready for 0.19, as we are planning to release it within the next weeks. There is no specific release date, but we will first update lemmy.ml to a release candidate, and if it works well publish the new release shortly after.
I didn’t get the impresssion that frontend and client devs have signaled that they were ready for a backend update to 0.19.X. And consequently lemmy.ml is still on 0.18.5.
appears broken for mlem as well
For the record, I realize that some users stated they were having issues using Memmy with this upgrade. Oddly, having made a test account here (obviously), I am not experiencing issues myself.
From my understanding the only change in authentication is that the JWT should be passed in the Authorization header instead of the request body. Does anyone know of conflicting information on that?
