Not sure if this is isolated to me, but when sorting by Active, my Subscribed, Local and All feeds pretty much don’t change for multiple days. I have to sort by New, Hot, etc. to get new content, but even those feeds stay somewhat constant.
Is this a problem with how the Lemmy feed algorithms work? Or is it a queueing issue, like how Mastodon refreshes timelines?
The algorithms I believe. Both active and hot are currently a bit broken, as are a few other things. Their biggest problem is they have trouble deprioritizing older posts, which leads to them getting more activity, keeping them high on the prioritization list. I’ve found sorting by new comments, new, and top (today) are really good ways to explore the site, and I’ve heard that the Lemmy devs are working on a fix for the broken algorithms. You can also hide read posts in your settings, though that has some drawbacks.
I’ve seen other posts say this is a bug introduced in the version of Lemmy deployed yesterday.
It definitely should be a top priority for the team to fix though — it seems to have really exacerbated the problem.
It’s a known issue on lemmy, the servers need to be restarted to refresh the front page
Lemmy is having growing pains and there are problems with internal tasks not updating the database correctly plus I’m sure individual instances would want to change some of these parameters to define what is ‘active’ in terms of age criteria, etc.
Same thing here, I assume it’s because the posts are still getting comments days later
