Sometimes with new users (especially on instances with not so many users), it happens that 1 user creates many posts in a short time.
2 example Screenshot, from the local timeline. in both cases, the local timeline contains basically only posts from 1 user.
this is different from spam, but in a similar way, slightly bad.
So, as a user, i would like to scroll the local timeline, but only seeing posts from 1 user in 1 community makes it uninteresting for me.
But when the posts are themself fine and good, it is not spam. So what i suggest is a change in the lemmy algorithm:
- when a user posts 1 post, nothing changes
- when a user posts 5 posts, which normally would be ordered directly after each other, other posts should be placed in between. So for the first post, still nothing changes, but the later ones are shown slightly below.
- the same for a community: i think it is desirable and makes lemmy more interesting if 1 community does not dominante the timeline even if it has many votes. i think it is desirable and increases the diversity, if other communities are moved in between.
yes i know the answer would be to open a ticket in github. this is not what my intention is here. I want consensus when we all agree on what is good, then a github ticket can be created or something.
(so my intention is also to talk about priorities, since just creating a github issue has a high likelihood to be forgotten)
I think this makes a lot of sense for the local and federated feeds. In fact i opened a very similar issue recently, but only regarding posts from communities. It should be pretty easy to implement the same logic for users as well.
i think it makes also sense for the ones you subscribe to. for instance, i have usually like 5 posts from lemmygrad in my feed because they have both many posts and many upvotes - which means high liklihood that their post lands in a high position in the feed.
compare that to instances which are for instance very new and get not many posts and not many upvotes, or only not many upvotes. --> i don’t see them much on my timeline
–> so i think applying that on all communities increases diversity overall, in the lemmyverse
@dessalines@lemmy.ml @nutomic@lemmy.ml
response to the linked github ticket:
instead of limiting the posts, i think the easiest way would be to just adapt the lemmy ranking algorithm https://join-lemmy.org/docs/en/about/ranking.html to include the amount of posts per user and per community. So that it is also logratithmic.
this is what i mean with the above post, that the more a user posts, slowly the ranking decreases for each post. Also for the community.
this is a better solution
deleted by creator
deleted by creator
Idk that’s how I use it too. I post what I read on my lunch break a lot
There’s an open ticket for that now.
An algorithm should be optional and opt-in, though.
Makes sense as long as I can configure it.
This sounds like a big fix for a specific issue. If I visit a new instance the default filter is active not new which I think is the right approach.
Otherwise it is a site admin/user problem not a lemmy problem. Some servers perhaps should just die off through inaction from the admin/users.
disagree. i found this issue many times in instances which whose activity was perfectly fine otherwise, and for instance even when the default filter would be active, this STILL would be an issue since every post is shown as equally active
I’m in agreement, but for the time being, you could try blocking the user.
Maybe, rather than changing the way Lemmy works, want you would want is a new “diluted” filter ?
I agree that would be an improvement.
