We’ve upgraded lemmy.world to 0.18.1-rc.1 and rolled back that upgrade because of issues.
(If you had posted anything in those 10 minutes between upgrade and rollback, that post is gone. Sorry!)
The main issue we saw is that users can’t login anymore. Existing sessions still worked, but new logins failed (from macos, ios and android. From linux and windows it worked)
Also new account creation didn’t work.
I’ll create an issue for the devs and retry once it’s fixed.
Edit Contacted the devs, they tell me to try again with lemmy-ui at version 0.18.0. Will try again, brace for some downtime!
Edit 2 So we upgraded again, and it seemed to work nicely! But then it slowed down so much it was unuseable. There were many locks in the database. People reported many JSON errors. Sorry, we won’t be on 0.18.1 any time soon I’m afraid…
Reasons I can think of:
The official Android client for lemmy, Jerboa, only supports 0.18 and later, unless users download older version from github and sideload manually.
Sorting is broken pre 0.18, new posts keeps flowing in.
Performance improvement by removing web socket from lemmy. (which fixes 2, which is why 1. happens)
Try wefwef.app on mobile
(no I’m not a bot account shilling I just really like the app)
Nice and thanks!
Question: Where’s the edit button? I can’t find it.
It’s an open issue on their github (https://github.com/aeharding/wefwef). Will probably be available soon, the development seems to be fast - I got two updates in a single day. Also tagging @kingcake@lemmy.world
Oye spaceduck, tas rechulo y lo sabes. !tip 12
Even that won’t work, because Jerboa initially tries to connect to lemmy.ml which is running 0.18, which older versions of Jerboa aren’t compatible with. The app just crashes instantly without giving you the opportunity to log in to your instance.
Jerboa works fine with lemmy world, it just gives a warning and crashes on occasion. Not an issue to use it though.
As a new user I tried logging in on Jerboa and it says the server must be on 0.18 and refuses the login.
Have you tried this fork? https://lemmy.ca/post/899342
Thanks for the link. I knew could side load an older version, I just wanted to be lazy and use something on the play store. I’m trying out several clients right anyway.
For me at least, I’m unable to change the community scope or sorting method. The only thing I can use Jerboa for is “local” and sorted by “active”. It isn’t totally unusable, but I would much rather be able to switch to subscribed and hot.
I had the same bug. A full restart of my phone seems to have fixed it.
Unfortunately that didn’t work for me. Thanks for the idea, though. I’m sure it will work for some. I suspect that if I wiped the app and set everything back up it might work, but that’s more than I’m willing to do at the moment and I can live with the inconvenience for now.
Alternatively, you can try this fork: https://lemmy.ca/post/899342
That sounds like Bethesda’s definition of “works fine”
It just works, it just works…
It works fine if you apply unofficial patch!
Yes, if you are already logged in. If you are not logged in, or get logged out you will not be able to log back in until the server version is above 0.18
The latest update of jerboa did not let me browse all communities. I had to sideload a previous version.
Unfortunately, the occasion seems to be at least once every five minutes for me. thisisfine.jpg This is not fine and definitely a major issue. Especially as we get closer to July 1. After this news from lemmy.world, I will have to switch, probably to Connect, until Sync arrives.
Have you tried this fork? https://lemmy.ca/post/899342
That is absolutely not “fine”.
Why the hell does Jerboa even limit support to 0.18? That’s so stupid.
Connect for Lemmy works better.
Is it open source?
The latest version only supports 0.18 because the backend works differently. Older versions of Jerboa support older backends of lemmy.
Likely because Jebora is written as a side project of the devs of lemmy so it’s always going to be cutting edge
I understand that. I’m not complaining about the quality. I’m just confused from a technical perspective why it doesn’t support rollback or older server versions in the event of…this.
Fixing the issues with posts appearing and scrolling the page the backend needed some pretty drastic rewrites. I’m not super familiar, but from what I’ve seen of the code, it would be a decent amount more work to support both versions.
Would it have been worth it? Yes, but it wasn’t anticipated that devs would stay on 0.0.17 for more than a day or two. With the time it takes for app stores to update, servers would have been updated before lemmy 0.0.45 was updated for the vast majority of users. At most, it would be a day or two instead of a week or two.