A posting on the Instance-specific issues/observations about the upgrade: https://lemmy.ml/post/1444409
KNOWN BUGS
- Searching site-wide for “0.18” generates an error. This was working fine in 0.17.4 before Lemmy.ml upgraded: https://lemmy.ml/search?q=0.18&type=All&listingType=All&page=1&sort=TopAll
Already noticing some major improvements in both UI and functionality. So nice to see devs that prioritize improving the platform instead of goofing around with dumbass money making schemes.
Yeah it’s much more eye pleasing now
Liking the new functionality so far! The spinner when clicking the upvote button is a huge improvement and lets you know that your upvote was actually received. I have noticed that some posts on my homepage show as expanded by default which is annoying (full size image/video instead of thumbnail) and this wasn’t happening before.
deleted by creator
I’ll wait a few days until it’s no longer a rc.
Same; I’m more of a stable guy :P
Upgraded my instance, switched the docker images to
0.18.0-rc.6and it started right up. Appears to have no issues for me thus far, so hopefully a full release will be right around the corner.Thank you for sharing.
This is so good!. Haven’t even updated yet, and I already see a lot more posts from lemmy.ml on my instance, and no more “Subscribe Pending”
I’ve been testing for hours, and “Subscribe Pending” went away for the first hour or so after the restart of lemmy.ml - but now I’m getting them again. The underlying issue still seems there.
It’s probably a combination of testing at scale on a server they control and wanting to get these features out so they can be iterated before a bunch of new users show up.
Wonder if I can finally sub to lemmy.ml communities…
From my remote instance, I’ve been subbing to lemmy.ml communuites about every 2 or 3 minutes, and it just now started to jam up. I’m speculating that the server restart fixed the problem for the first hour or so, but now it’s back. Open GitHub Issue: https://github.com/LemmyNet/lemmy/issues/3101
It’s just so odd that only lemmy.ml communities seem to cause this. Lemmy.world is around as big or bigger and no issue there.
I think lemmy.ml has more posts, comments, likes in the database due to historic reasons - and the backend is timing out, PostgreSQL not keeping up to application timeout. I have seen the problem on Beehaw, Lemmy.world when they are busy and throwing nginx 500 errors on their front page.
deleted by creator
I can confirm that.
Not long after you upgraded, I upgraded, and was able to successfully subscribe to things here.
But… not now. /sadface.
Where can I see the list of changes?
You can load the project directly in GitHub and do a diff between 0.17.4 and 0.18.x.
Here are the diffs (0.18.0 vs 0.17.4)
Can you link it for a non techie?
Also- be aware enabling the new 2FA option… It didn’t work too well for me.
Knock on wood, I tested it in an incognito window before logging out- and was able to disable it when it didn’t work.
Awesome news! Looking forward to the finished release.
Can we please not have a default avatar? I specifically want no avatar.
Hard disagree, and in fact this was one of my early complaints, and a pretty serious usability issue: because some accounts had an avatar and some didnt, the justification was all over the place, making the scanning of usernames and community names a real chore and tiresome.
Wether you like the default picture or not, well I guess that’s a matter of personal preference. You could always upload a black box for yourself (or even a transparent PNG?).
But that aside this is objectively better UX.
The good news is, there are so many front ends in development, we’ll all quickly find a UX tailored to our needs.
I’m getting a lot of syntax errors at the bottom of the page since well… recently.
SyntaxError: JSON Parse error: Unrecognized token ‘<’
deleted by creator
I get this too on safari on ios
I’m on Safari Mac. If that helps anyone…
Can anyone explain why lemmy decided to remove websockets, what they decided to adopt instead of websockets, and to what extent websockets are being removed? I still feel like I don’t understand this move (but I’m sure there’s a good reason)
The primary reason I suspect is that it was buggy code. You would be reading a post and the votes and even the title and body of a post would just change in front of you to the wrong post. The server wasn’t keeping the index of clients correct or something. It was a very uncommon way to build a webapp
Websockets really don’t integrate well with the entire rest of the HTTP stack, instead just repurposing the socket as a free-standing two-way communication pipe.
You can definitely use websockets for requests like regular HTTP, but you have to reimplement things like cookies/session handling, request resumption/retry, duplicated request detection, request timeouts, authentication, etc yourself if you want to use it that way.
I personally much prefer regular HTTP requests for queries/RPC, and HTTP SSE for notification streams, since those are well developed technologies in the web space - and work much better if there’s a middleware in between.
This update removes the captcha option still?
If my brain is interpreting correctly, they committed it back in yesterday: https://github.com/LemmyNet/lemmy/pull/3249 before 0.18.rc6 was tagged.
cool shoulda thought to check that thanks
Unfortunately the PR doesn’t appear to have been merged. All the commits have been made only to the branch pertaining to the PR, unless someone manually copied the code to main (why?)
Awesome! Thank you for posting this. I will be updating my instance as soon as I can.
