In the screenshot you can see that there is currently one rising community overloading my post feed. I assume this is happening to many users. I understand that I can block the community but that's not really what I want. I think that this problem could be solved by introducing a mechanism to dynamically limit the number of such posts based on user preferences. For example I could set this community to appear less often and an algorithm could apply this preference to my feed order. I know that the proverbial algorithms used by major social networks are frowned upon. That happens for a good reason - they are opaque, proprietary and often show signs of bad intention. They are used for political and social influence, to silence opposing voices and a whole array of other nefarious goals like playing of people's fear, outrage, etc. The thing I'm suggesting would have to be transparent by design and fully optional. That's a social media "algorithm" I'd like to use. I'd like to hear what other people think about this idea.
Algorithmic post ordering
6 Comments
Die4Ever@programming.dev · 7 pts · 1y
I think even just a frontend (web UI or mobile app) could fix this pretty easily
when it loads a page with many posts from the same community, it only shows 1 or 2 and puts the rest in a queue to show on later pages
gressen@lemm.ee · 5 pts · 1y
Sure, it could work as a client-side filter but then you need to develop the functionality for multiple clients.
Die4Ever@programming.dev · 3 pts · 1y
Yep. But it could be seen as an advantage your app has that others don't, and different apps can try different approaches
Rentlar@lemmy.ca · 5 pts · 1y
Mastodon's filter system works wonders, where if you're seeing too much of some keyword you can block that temporarily or permanently, and either erase it entirely from your feed or hide matching posts in a spoiler. It would be awesome if something like that could be adapted for Lemmy.
For current client-agnostic solutions, you can do any of the following on Lemmy:
catloaf@lemm.ee · 4 pts · 1y
That gets very complicated very quickly. I would just choose a different sort algorithm from whatever you have there (hopefully not new). And I would also not use the All feed if you don't want an unfiltered feed of everything as it is.
glowing_hans@sopuli.xyz · 2 pts · 1y
Random slots, where random posts (age/upvote count does not matter) are introduced and marked as such could help in such a problem without complex systems.
The proportion of these random slots could be a user-setting.
Something similar to this: https://en.wikipedia.org/wiki/Wikipedia:Random Does this exist in lemmy (backend) api?