5
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Jun 2023
5 points (100.0% liked)
Asklemmy
42525 readers
1888 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
I've seen like 5 different posts about this already, I guess I'll reply to this one too xD
Lemmy "Hot" ranking is currently kinda broken. There's an edge case that stops the hot_rank column from decreasing, meaning the post never goes off the front page. Will be fixed in 0.18.
Do you know when 0.18 will be out?
Trite answer: When it's done
More in-depth answer: Currently there's no set date. It depends on how quickly they can tear out all the WebSockets code and replace it with simple HTTP (that's the BIG change, will fix a lot of different things), and then test those changes. The hot_rank fix has already been merged, that's done, but they want a stable, cohesive release with all the good stuff.
Current estimations I've seen range from 1-2 weeks, but it all depends on how fast they can get it coded and tested.
Why are they getting rid of WebSockets? It's really useful for instant data and is often faster than simple HTTP requests.
You can see the discussion about this here, but the short version is that it's not scalable, hits apps & browsers like a truck, memory leaks, and live updates cause feed reshuffling which is really annoying