Hello all! I am posting from my own self hosted instance, running 0.18.0, but this issue existed in 0.17.4 as well. When sorting posts from my subscribed communities by Hot, I will get a handful of newer posts, followed by an entire page or two of old posts going as far back as 4 years (not with new comments), before finally seeing fresh posts again. Thus far I have been scrolling past all the ancient posts every time I open lemmy (both through Firefox and jerboa) and going straight to the fresh content, but since the issue wasn’t resolved with the new release I’m wondering if anyone knows what is causing this behavior and if there is a fix. Thank you!
You must log in or register to comment.
Sorting was borked in v17, and fixed in v18. It seems there is some bugginess with going from the borked v17 to the working v18, I too have a random set of 3 year old posts that keep appearing. But they are slowly disappearing for me as time passes, now that v18 is properly updating hot sorting.
Thank you, I’ll keep an eye on it and hopefully it will slowly fix itself as well
I have the same, new install of v18 and a lot of my posts are from more than a year ago. Even a lot of the “newer” are over a month old with a single upvote and no comments. It’s made “hot” pretty much useless for me.
Yeah, I’m hoping it will clear up with time as other commenters have suggested!
I’m hoping so. I also noticed avatars aren’t showing on other instances either. Seems there are a few bugs, and if the github is anything to go by, the devs are going to be extremely busy for quite a while.
i think the bug that caused old posts to always appear as hot in 17.4 just made those posts rank higher than other ones, but thanks to 18.0 they’re finally getting pushed down. IMO this will fix itself organically.
Thank you for the input, I’ll keep an eye on it and hope it fixes itself with time.
I really wish, as in [email protected] - that each instance could easily adjust these parameters.
I thin it would also be nice as a server operator to have a button to trigger a sort rebuild on demand, not just the internal schedule timer.
