Official Announcement: https://lemmy.fmhy.ml/post/263377 Github Release Page: https://github.com/LemmyNet/lemmy/releases/tag/0.18.0
This is a massive upgrade, and a lot of the minor annoyances that users were finding about Lemmy has been fixed. You can check the above links for all the changes implemented but some of the major ones are:
-
Websockets replaced by HTTP: What this means for you is that instances will feel snappier due to less load, and the annoying sudden flood of new posts when browing hot is also gone. In general hot/active sorting has been reworked and feel much better to browse.
-
Links that would take you off-instance should now get automatically converted to ones that don’t. And just writing the name should be enough to turn it into a link. So no more manually searching for the linked communities you find in the comments.
-
Support for 2-Factor Authentification.
-
Custom emojis for Instances.
-
Support for PWA.
-
A Share Button.
-
Improvements to overall look and feel of Lemmy.
Not to mention many under the hood changes like database optimizations and bug fixes. This is a very big version upgrade that’s come at just the right time.
However, some Instance admins encountered errors when trying to upgrade. And captchas, which we rely on to prevent bots from flooding in, will come back only in version 0.18.1.
So our options are to either upgrade now, maybe have some downtime and to turn on registration applications, or wait until v0.18.1 is released before upgrading (which shouldn’t take more than a few days). We are leaning towards option 2 for now, but interested in hearing what others have to say.
The continuous refresh makes the site mostly unusable for me in browser. I’d prefer updating to fix one of the biggest bugs the site has
2FA is something I’ve been missing honestly, but I can wait until v0.18.1 for more stability. Thanks for the change log and the developers of Lemmy for this awesome update.
Waiting for 0.18.1 seems like the safe, smarter option to me
yea not all instances are 0.18 sadly :(
If it really is only a few days, yeah, I’d wait it out.
v0.18.1 is released before upgrading (which shouldn’t take more than a few days)
A bird in the hand is worth two in the bush, and an update that fixes bugs which break basic functionality is worth upgrading for immediately rather than waiting for over-the-rainbow. 2FA alone makes it pretty much not a realistic discussion, honestly.
Things are working, no rush for new things or major change. Prioritize ease of administration over immediate need for new toys.
I updated my small instance, it worked great. Until I rebooted the server then it stopped working entirely. I tried restarting the database and the app separately, but it never came back up. I had to wipe and reinstall as downgrading didn’t work either. Due to issues with names no longer federating if the instance is recreated with the same domain and name I had to change my subdomain entirely as well. If for example a user was named user1@instance1.tld and you reinstall that instance using instance1.tld. If you recreate the user user1@instance1.tld, it will not federate any comments.
I may be a small use case, but it has made sure I’ll be waiting a good long time before upgrading again.
To me personally the websockets thing make the site pretty much unusable. So I’d prefer to upgrade earlier.
whats the problem with websockets?
The bug where your feed keeps being flooded with posts from the top, thus pushing everything down. You can’t click anything while that happens.
I’d be keen to hear about how websockets are slowing down Lemmy and how much of an impact this update will have.
kbin works on sockets for it’s messing from memory, but I haven’t dug to deeply into it
I’d vote for waiting for 0.18.1 if it’s only a couple more days
I think you should go for option 2!
It’s a good idea to keep it stable but I will have you know that updated jerboa users can no longer login to your instance.
Can’t log in, or get the annoying pop-up? I’d rather wait till the full upgrade is ready than have the sever go down twice in a week.
Jenora crashes every few minutes or lesser after the update. practically unusable right now
Hmm… I’ve been using Jerboa since I signed up about a week ago. It’s not perfect, but the only problems I had was last night when my router and access points went offline to update…
Also, I have been using Jerboa for the last 10 hours with minimal bugs…
Can’t login at all.
Sounds like a good update, a couple of days shouldn’t matter but I can see both sides to it, people want the latest and greatest but also if there are any issues that’s not great as more people migrate to Lemmy
I sat wait. Right now Lemmy and this instance are working and usable. IDK why they’d pull captcha given the number of spam bots but that’s worth waiting for IMHO especially if it’s only a few days.
I remember reading through a discussion in which the dev popped in to explain their reasoning, maybe a Github issue? but yeah, if it will only be a few days work to implement a different capcha, probably better to wait.
I don’t get why not wait a few days for the release then? If the problem is that easy to fix, is there some other issue that needs to be released ASAP?
That’s just what they decided to go with. I think it was a decent decision given the usability and stability problems that were made apparent when people started coming in droves during the blackouts. Now instance operators have a choice; upgrade and lose captcha temporarily (those with email verification and applications less affected here), or wait for 0.18.1 when it’s slated to be implemented.
Over here we already have 0.18.0, it’s very nice, but if there any concerns I’d rather wait.
Updating now and closing new user registrations for a few days is an option? I understand that it would be a problem, but it is supposed to take a few days
In any case what you decide well done will be
Seems a shame to close new user registrations during a period of rapid growth and mass exodus from Reddit.
FWIW I’ve upgraded aussie.zone to 0.18 and encountered no isses, apart from the removed captcha support. But my instance isn’t huge by any means.
