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

Duplicate Pages Across Fediverse (kbin.social)

submitted 1 year ago by Calcharger@kbin.social to c/fediverse@kbin.social

9 comments fedilink hide all child comments

So I notice that KBIN and BEEHAW and LEMMY all have duplicate pages dedicated to the same content. Are we as a community going to have to decide which page will be the 'main' page, will we have to subscribe to each magazine for each instance, or will they consolidate eventually?

So like, theres a technology@beehaw, a technology@lemmy, and a tech for kbin. Does it make sense to spend time cultivating one, if another ends up getting more attention?

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

[–] Otome-chan@kbin.social 1 points 1 year ago

They're not really "duplicate". Each instance has it's own magazines/communites/whatever, and those can have different rules, moderators, etc.

If you want to follow all of them, then follow all of them. If you only want one of them, then do one of them. Reddit had various subreddits all on the same topic, for instance /r/technology and /r/tech, and they had their own nuances, users, rules, etc. One might end up being more popular than the other for whatever reason.

Also keep in mind that they're subject to rules/moderation/control of the instance they're on. I'm using kbin.social, but if beehaw decides to do some weird thing or decide they no longer want a technology group, it's basically out of my control. Whereas a technology group here on kbin.social wouldn't be effected by beehaw's stance for their instance as a whole.

I imagine people interested in a topic will just follow all the related groups unless there's an issue with one of them.