Lemmy hotfix for home page bugs...
Lemmy hotfix for home page bugs...
Hey guys, as I'm sure many of you are already aware there's a couple of bugs that are plaguing the home page. I've made a hotfix for these bugs:
- New posts popping up and pushing all the other posts downwards - this is more prevalent on the larger lemmy instances, you'll just be scrolling and suddenly everything's pushed down because new posts are being added to the top of the page as they're being created
- Default "All" not working - this is more something admins would be aware of but in the site settings you can set the default "Listing Type" to "All" instead of "Local", but if you do this the home page doesn't properly load "All", it'll show you the "Local" feed with "All" selected in the tabs. Seems this feature wasn't implemented correctly in time for 0.17.4
Since 0.18 is still a little while out, and I'm sure the devs are both really busy on it (they also said they won't be making another 0.17 release), I went ahead and made a hotfix for these. I have it up on jcgurango/lemmy-ui:0.17.4-hotfix so if you're using docker you can just upgrade to that image. I'm not really sure how ansible works, so I can't help with that.
Here's the repo I have these changes on for those who want to check or build it themselves: https://github.com/jcgurango/lemmy-ui - I've based it on the v0.17.4 tag on the upstream repo.
You're viewing a single thread.
Would this be good as a PR?
I read in one of the PRs they aren't doing another 0.17 release, and the first issue is already fixed in 0.18 since they're removing the WS client
What does WS mean? I hope it's not Web Site
It means websockets, they way it's implemented throughout the website has been a cause of a lot of headaches and they were using it for things where it really wasn't needed. My hunch is it was to lessen the bandwidth usage but I wonder if that's actually worked out.
Things that are obvious in retrospect! I saw WS and my brain went straight to web site 😆 and I couldn't think of anything else.
My hunch is it was to lessen the bandwidth usage
WS is probably more resource intensive than regular HTTP because it requires an active connection, whereas HTTP creates a connection and then tears it down. Devs have said they're removing WS to reduce load on the server.