this post was submitted on 14 Jul 2023
14 points (100.0% liked)
Fediverse
19 readers
2 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 this is a good idea. Keep in mind that different instances have different policies, moderators, and users. This leads to different rule enforcement, culture, and federation status. Even if a magazine/community has the same name and the same discussion topics does not mean it's the same group of people reading those posts (some might be, due to cross-instance federation, but not all will be). In short, they are different groups and cannot be treated as the same without pissing off people.
The proper solution is to let each community just evolve until one naturally emerges over time as the go-to community or they all differentiate themselves enough to be considered different (albeit with similar names). Adding a bot to cross-post content just slows that process down and makes the problem persist for longer. If a topic is truly small enough that getting enough people for critical mass is difficult (like your DIY cobbling example), then it shouldn't be hard to start a discussion in each of the separate communities to suggest assigning one as the "main" one and then just stop using the others. This is something that should be driven by the communities, not the software.