this post was submitted on 28 Jun 2023
259 points (97.8% liked)
Lemmy.World Announcements
29201 readers
23 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news π
Outages π₯
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations π
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just curious, why are we updating now instead of waiting for the proper 0.18.1 release?
Because of a few things, really anoying bugs and the Jerboa app not working properly with older versions
For example the frontpage is no longer being constantly filled with random posts when you set the filter to "active" or "top day".
Federation is completely borked with .18 servers. Its very difficult for us to interact with https://lemmy.ca in any way: subscribing, upvoting, comments, posting... its all bugged.
Its maybe not that big a deal because Lemmy.world "has the most users", so in some regards its https://lemmy.ca's loss but... we need to restore reliable federation... especially before the July 1st rush IMO.
The .17 to .18 upgrade is basically a soft-defederation event, because of whatever this bug is between the two versions.
Ah that explains it. Someone posted a cool photo to my community from lemmy.ca but didn't interact further. Looks like my comment didn't even show up on their end.
Anyway, thanks to everyone working on the issue. I know these things aren't easy.
I'm subscribed to lemmy.ca and programming.dev, both of which are .18 now. Feels kinda bad losing access to those communities while this issue is getting worked out...
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.
That sounds like Bethesda's definition of "works fine"
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
As a new user I tried logging in on Jerboa and it says the server must be on 0.18 and refuses the login.
The latest update of jerboa did not let me browse all communities. I had to sideload a previous version.
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.
That is absolutely not "fine".
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, until Sync arrives. Update: Liftoff is fantastic, give it a try!
Have you tried this fork? https://lemmy.ca/post/899342
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.
I suspect there will be a large influx of new users in two days, and that having Jerboa not working on .world might cause a few issues
I thought because right now on 0.17 mobile access with jebora is pretty broken and since 0.18 .0 is not an option they are trying to go to 0.18.1 as soon as possible. Even when it means installing rc versions
UI at 0.18.0 and backend at .1rc1
Yep we tried bringing both the UI and the backend to 0.18.1-rc1 but that gave issues. Lemmy devs told us to try this combination and that seems to work. π€
A Release Candidate is supposed to be past beta testing already and in a state of no major bugs.