Most of the communities are on one instance i.e .ml. Should we spin up more instances and start spreading communities either by location, interests, etc? Maybe, I am wrong but do mod/s who run the communities understand the idea of “decentralized social networks” or this is just to get few brownie points to start the community and increase the traffic? Please correct me if I am wrong.

No offence, just an observation.

  • @zksmk@lemmy.ml
    link
    fedilink
    12
    edit-2
    3 years ago

    There are benefits to each community being local and server specific (moderation, culture, community), but there are also benefits to the idea of a single community being spread over multiple instances (decentralisation, resilience, activity/reach). There are reasons why few people want to start a or post content to a community on a random server, and most people opt for the biggest one. There’s relatively few people as it is already and creating duplicates, fragmentation and inevitable manual content replication doesn’t seem like the way to go about things.

    This is why I like the idea of a potential future feature where on top of /c/acommunity we would also get a /t/atopic that aggregates all the communities with the same name from all the instances into one place/feed. This would NEED to be optional and the community mods would have to have an optin/optout feature for their community being included in the /t/topic feed. I think that would make both sides happy.

    As it is, I don’t see having active communities on other instances likely, unfortunately. Individual accounts can work just fine from other instances, and the content gets auto replicated, but the parent hub is still in one place.