The past couple updates whenever I’m browing “all” with sort set to “hot” the first few pages of scrolling is accurate but then it turns to posts that are 6months-2years old. This is only after 1-2 minutes of scrolling. Has anyone else had this issue?
Yea this is a Lemmy issue, not an app-specific issue.
“Top 6 hours” has been giving the best experience to me. Hope they fix the “hot” bug though.
Top 6 hours is great but it’s easy to get to the end of all the post with the 6 hours setting, especially when you don’t subscribe to the spammy meme communities so I tent to lean more to top 12 hour or top 1 day sometimes too.
This is a known issue in Lemmy : https://github.com/LemmyNet/lemmy/issues/3428
Looks like a fix will be available in the next release:
I’m having this issue as well. Tons of years old posts.
This is just a guess as I haven’t looked at the source code for anything, but I think this is because instances may take a long time to get all the old posts from a community when they first start getting ActivityPub updates from it (when a user first subscribes to the remote community). When sorting by hot, it seems like the time the post was received via ActivityPub is used for sorting instead of the time it was originally created.
Just started using liftoff for lemmy. I think it’s fine and usable. Can see new posts on hot.
This is for connect, not liftoff
I’m also on Liftoff and seeing the same issue as OP. I think this is a server side problem.
All apps just pull content from lemmy. It’s absolutely a lemmy thing and Hot has been like that for a while. Top for the last 6 or 12 hours is a better “front page” feed for now until they improve Hot.
It’s even more inaccurate than that. Look at the time a post has been up then look at comments. They are often older than the post. I see posts all the time that say they are posted “now” with comments an hour old.
