this post was submitted on 21 Jun 2023
122 points (98.4% liked)
Fediverse
42 readers
5 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think the architecture has anything to do with it. The algorithms just need improving.
There's no algorithm in the fediverse. That's one of the main selling points.
The feed present on Kbin and Lemmy that delivers content that is "hot" is still an algorithm, it just isn't a hyper-specific one like you'd see on Tik Tok
Sorting by new also is an algorithm.
Not trolling here: I think this is something the fediverse will need to decide at some point. What are the acceptance criteria for timeline presentations? But this would also be a perfect example of diversity: don’t like the way our instance sorts your timeline? No problem, here’s some instances that do it differently.
The goal should be to allow users to choose their own algorithm, including third party algorithms you can install yourself or something.
Sure, but the algorithms themselves will have to be provided by the instance, so I guess different instance might make different choices, for example due to privacy concerns etc.
You could engineer it so users could provide their own algorithm.
It would be a HARD engineering problem, but not impossible, IMO.