this post was submitted on 18 Jul 2023
578 points (98.5% liked)
Fediverse
28748 readers
20 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If a community has grown a lot, unfortunately it takes up all the posts on the homepage. If I were a developer, I would sort by weighted success. For example, if the "x" community has 1000 subscribers and the post gets 100 likes, it has ten percent success. If the other 'y' community has 100 people and gets 11 likes, it has 11 percent success. This overrides the post in community x because the post in community y is more successful. This is the logic of 'weighted success'. With this logic, a better ranking formula can be created.
I figured that's what Id see sorting by New Comments but that hasn't actually been the case. Any new post or post with a new comment gets pushed up to the top immediately and doesn't even take into account votes, but even refreshing the page all day doesn't catch a lot of small communities unless they are also attracting attention.
The thing is, a 10% upvoted post on a 10,000 people community is more popular than a 90% upvoted post on a 1000 people community - those 10,000 people in the former community are 10,000 people interested enough in that kind of thing to subscribe, whilst only 1000 people are interested enough in the other kind of thing.
So it does make sense to put the former higher up in the global page when sorted by popularity because globally that post was more popular.
However I do think there should be someway to as a user push down posts from certain communities without outright blocking the whole thing: maybe som throttling-down based on the rate of posts per time (i.e. the upvote threshold for posts from a community to come out in All depends on the number of otherwise qualifying posts in the last X days/hours, thus explicitly targetting the "flooding with posts" itself) rather than the straight count of upvotes or the proportion of upvotes that you suggest.
That said in the meanwhile I'm really tempted to block the more generic meme communities.
General popularity is not a good metric IMO. If I like a community, then it shouldn't matter if a million people like or it's only me and my cousin. If the community likes the content, I want to see it.
It's trust between the members of a community.
However, weighted sorting is not a solution too, upvotes counts are not linear. Maybe, quantile sort?
What's liked by the general population is a good metric for providing general stuff to the general population and that's what we're talking about in All.
That average can however deviate a lot from the sweet spot for some people, quite possibly a large minority (even the majority depending on how concentrated or not people's tastes are around it).
Something that looks at your previous choices (or even generally stated choices in the form of communities you subscribe to or block) similarly to what some search engines and some social media sites will do, can shift that toward more your own specific tastes, but that's computationally more expensive and requires more users and more user data to get better results (basically it's finding certain kinds of users and local minima which are more satisfactory to them).
I suspect something like an AI solution (not LLM, just a much simpler neural network) running on your own device that tries to predict what you're going to click on and learns with what you do (or not) is the only way for a personalized "no fluff on my feed" solution, but that's for apps running on top of Lemmy, not the Lemmy engine.