PSA: Lemmy 0.18 is rolling out in produciton, lemmy.ml has already been upgraded to BE: 0.18.0-rc.6 - the "websocket webapp" removal
3 years ago by RoundSparrow to c/lemmy
A posting on the Instance-specific issues/observations about the upgrade: https://lemmy.ml/post/1444409
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.
Thank you for sharing.
Already seeing a positive difference on lemmy.ml. Better feed content and no more posts being added constantly to the top when you browse All
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.
Where can I see the list of changes?
Here are the diffs (0.18.0 vs 0.17.4)
I'm curious why especially lemmy.ml wouldn't wait for full release - surely after 6 RCs the full release is imminent?
Or of course, they're stress testing it. Makes sense enough.
Wonder if I can finally sub to lemmy.ml communities...
I'm curious why especially lemmy.ml wouldn't wait for full release - surely after 6 RCs the full release is imminent?
lemmy.ml is official developer instance, makes moste sense to test it out here after dev servers.
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
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.
I've also been seeing issues with subbing to lemmy.world communities from lemmy.ml, so I am not sure if it's limited to just lemmy.ml communities.
I can confirm that.
Not long after you upgraded, I upgraded, and was able to successfully subscribe to things here.
But..... not now. /sadface.
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.
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.
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.
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?)
I'm getting a lot of syntax errors at the bottom of the page since well... recently.
SyntaxError: JSON Parse error: Unrecognized token '<'
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.
Might be uglier... but, it follows normal web standards now.
I mean, you can parse a URL path and query string however the heck you want. You can make the former order independent, but it's probably better supported in libraries as the latter and definitely more common and obvious for users.
Thats literally how most websites handle http GET parameters
@lemmy.ml
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
go to feed...
@lemmy.ml
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
go to feed...
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.
save