Wow that release is huge. Look at all the server and ui bug fixes. Going to have to chuck some money to the lemmy devs they've clearly been working hard.
this post was submitted on 23 Jun 2023
13 points (100.0% liked)
Lemmy.nz Support
345 readers
1 users here now
Ask your questions here
founded 1 year ago
MODERATORS
This release has 46 contributors! Compared to the 17.4 release that had 3, or the 17.3 release that had 4. It's such a massive release, and with so many new users it has attracted many new devs!
That's awesome news!
This might be a dumb question, but where do you go to do that? I'm chipping in for server costs here but haven't given the lemmy side of it much thought.
Not OP but donation info is here https://github.com/LemmyNet/lemmy#support--donate
I've recently done a donation, I think lemmy is great.
Thank you!
Thanks! What is the breaking change? I know the backend and frontend can't be combined with older versions (i.e. you have to update both at the same time), if that what you're referring to?
They have removed web sockets. That is a massive breaking change.
Yes, for the front/backend connection. I'm just hoping there is no change needing us to rush to 0.18
Fixing the hot/active sorting will be super helpful
Yeah, definitely. But the lack of capcha and the fact there's a bug where a remote user can cause an admin account to be un-admined (locking admins out of those settings), well I'm definitely considering waiting for 0.18.1
Didn’t know about the admin lockout bug, that sounds serious.
The steps to reproduce don't seem to have been tested but the current theory is that if a user is federated to a server that has an admin with the same name, and then that user is banned, then it may cause the admin to be un-admined I guess due to an update that doesn't correctly distinguish the local and remote users.
Honestly, it's annoying but may not be a showstopper for upgrading to 0.18
You can fix it by changing the flag in the database, and it's not giving the admin permissions to another user which would be a big security problem.
Hi @Dave@lemmy.nz my Jerboa app (Android) has auto updated overnight and now I can no longer log in that way as it requires 0.18. Guess I'm not the only one. Did you decide yet if you want to upgrade to 0.18?
I did not know that! Thanks for letting me know. I will make upgrading a priority, though we will probably need to turn on registration applications as the cloudflare bot detection doesn't seem to be working
Yeah it's a bit annoying that they didn't deprecate it instead of just ripping it out. Anyway, I see you've updated it to 0.18 :) Hopefully all goes well!
There was a technical reason. This version removes websockets, which has performance improvements and solves a lot of outstanding issues.
Unfortunately the current captcha relies on websockets. The option is actually still there, it just causes an error on the registration page, stops registration from showing, and still doesn't actually show a captcha.
Long story short, it's just broken rather than deliberately removed (though originally they planned on dropping it which is why no effort went into solving the issues.
why did they do that?
See the linked post, essentially for performance.