sh.itjust.works Main Community

7718 readers

1 users here now

Home of the sh.itjust.works instance.

founded 1 year ago

MODERATORS

TheDude@sh.itjust.works

manifex@sh.itjust.works

biela@sh.itjust.works

imaqtpie@sh.itjust.works

Timeline not changing frequently? (sh.itjust.works)

submitted 1 year ago by httpjames@sh.itjust.works to c/main@sh.itjust.works

10 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] thesanewriter@vlemmy.net 21 points 1 year ago (1 children)

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.

[–] CoderKat@kbin.social 3 points 1 year ago

I think there's definitely some algorithm changes needed. I've noticed some weirdness with kbin's hot algorithm. In comments, it often puts comments with no votes or just one vote near the top, which doesn't make sense.

I also notice the front page hot algorithm has a duration option, but it doesn't seem to change anything.

And the top sorting looks like it might be local only?