Fediverse

287 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 [email protected] to c/[email protected]

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

[–] [email protected] 2 points 1 year ago

But this means there needs to be someone monitoring posts, not just every five minutes, but every five minutes, for every server.

This is completely untenable. An off-instance sub might not even have enough subscribers on that other server, to count on both hands. Yet someone has to mod it? For small communities, there might just be one or two subscribers to it per server.

You're giving examples with massive usercounts, which wouldn't work, due to that massive usercount. But low usercount examples also don't work, due to the low usercount.