It's coming. You said that 'it's been fixed in a recent release', but no, it's been fixed in latest version they're working on right now that hasn't been released yet. There is a release candidate being tested, but it has a few bugs still so there will be at least one more release candidate that has to be tested for a bit before being released.
this post was submitted on 19 Jun 2023
26 points (84.2% liked)
Lemmy.World Announcements
29046 readers
5 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 [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (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 1 year ago
MODERATORS
That's true, though the dev has already patched his deployment on lemmy.ml. Hopefully the release is dropping soon.
There was an attempt to patch the server to the first release candidate two days ago. It didnโt went well: 500 error appeared, and the patch was reverted. You may see the details here: https://lemmy.world/post/226641
It doesn't look like 0.18 is out yet
The issue is closed because it will be solved in the next big update. Scroll further down and you see:
This issue is likely irrelevant due to migration away from websocket usage in 0.18, I believe this issue can be safely closed.
Unfortunately no one seems to know when they will drop 0.18.