Fediverse

3 readers

1 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

Why can't magazines/communities aggregate content from other instances? (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by timbervale@kbin.social to c/fediverse@kbin.social

137 comments fedilink hide all child comments

When I look at https://lemmy.ml/c/startrek vs https://kbin.social/m/startrek I see two entirely different lists of posts. Why? It's the same topic, just on different instances. How can we have communities about topics without having them siloed into their own instance-based communities? Is this just related to that 0.18 issue with Lemmy/kbin not talking nicely, or is this how the Fediverse is?

Is it (at least theoretically) possible for me to post an article on https://kbin.social/m/startrek and have it automatically show up on https://lemmy.ml/c/startrek, or are they always going to be two separate communities?

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

[–] timbervale@kbin.social 1 points 1 year ago* (last edited 1 year ago)

Kind of, but not exactly. I'm asking for a solution where kbin.social and lemmy.world and startrek.website all post to the exact same community, but in a way that doesn't require me to be subject to the whims of the mods of any specific instance.

If a mod on !startrek@startrek.website (currently the largest Star Trek community instance) were to go on a power trip and ban anybody who mentioned Star Trek: Discovery, I wouldn't want to be part of that community, anymore. Most people wouldn't care, though, and just wouldn't post about Star Trek: Discovery. So, fine, I go subscribe to another instance where they allow Star Trek: Discovery, but if !startrek@startrek.website has 20 million subscribers, and the next biggest instance only has 40 thousand, the experience of using that next biggest instance is going to suck in comparison. That's the problem I'm trying to find a solution to: a situation whereby a specific instance doesn't control the content for everybody, but instead they only control the content for their specific instance.