I don’t understand how Lemmy intends to do it when the different instances are federated, if several instances create the same community for example…is that possible?

    • TrollOP
      4·
      5 years ago

      But this means that there can be dozens of different “#opensource@server.tld” rooms, so it would mean that a user who is interested in the topic “opensource” would have to subscribe to all the different rooms?

      #opensource@one.tld #opensource@two.tld #opensource@three.tld …

      I thought that if instance A had a room named “#opensource” instance B couldn’t open one to avoid duplication.

      • AgreeableLandscape
        2·
        5 years ago

        It’d be pretty easy to have a “subscribe to community on all supported instances” to auto-subscribe to all the communities with the same name on instances your root instance federates with or doesn’t block, and you can then go in and refine your subscription options by selecting and unselecting individual communities.

        A bigger problem is what we should do with communities that are dedicated to the same topic but have different names. Like /c/foss and /c/freesoftware.

        • AgreeableLandscape
          3·
          5 years ago

          I think Prismo doesn’t even have communities. Their model is one instance per topic.

    • AgreeableLandscape
      3·
      5 years ago

      You can tag communities with # and users with @ on Lemmy, so they would be the logical choices. But if we’re going with the Mastodon model it should be @user@lemmy.ml and either #community@lemmy.ml or #community#lemmy.ml.