So far for me the process is very convoluted:

  1. I go to https://browse.feddit.de/ and find the community.
  2. Then I need to copy it’s name.
  3. Then I need to go to my particular instance (lemm.ee)
  4. Then I type manually in my browser address bar lemm.ee/c/<communityname>
  5. Then I go back to https://browse.feddit.de/ and copy the address of the original instance of the community.
  6. Then I go back and add the original instance address to already typed thing in step 4 like this lemm.ee/c/<communityname>@<originalinstanceofcommunity>
  7. Then I can finally subscribe!

Oh my God! Please, tell me there’s a better way of doing this!

EDIT: There is a better way! Solution is to … use the search function in your instances home page and select community (if it exists already) and search. This way I don’t need to go to browse.feddit.de anymore. And links will take me straight the the communities “reflection” in my own instance, where I can subscribe.

  • BrunachoEnglish
    0•1 year ago

    Step 6 will return you a 404 - comunity non existent if your instance is not federating with the instance of the community you’re looking for.

    I do:

    1. Step 1.

    2. Copy the URL

    3. In my instance, I use the search fuction. I search for the URL. The community is one result.

    4. enter the result, the instance has begun federating.

    5. subscribe.

    • @[email protected]OPEnglish
      0•1 year ago

      Wait, you can force your instance to start federation with another instance!? Did I understande you correctly?

      • BrunachoEnglish
        1•1 year ago

        Not exactly force. It’s by design. Instances don’t federate with each other unless a user of one wants to communicate with the other (via subscription, or commenting, or whatever).

        But instances can block each other and if that happens, there’s no way you can access from your instance.

        What usually happens is that big instances (like lemmy.ml), just by the mere fact that they are big, are probably already federating with your instance anyway so you may not have encountered this situation.