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.

  • @JackOfAllTraits@lemmy.world
    link
    fedilink
    English
    01 year ago

    Huh, I didn’t know this! I think that this could be solved by smaller servers making a bot account that su subsribes to all avaliable communities?

    • @foggenbooty@lemmy.world
      link
      fedilink
      English
      11 year ago

      I suppose you could, but it’s done this way on purpose to reduce load on the server. As soon as a user from that instance starts flowing the community from another instance, that server has to keep track of all updates in that community to be able to deliver it to you.

      Essentially, if none of the instances users are following that community, why bother with keeping track of it. If you wrote a bot to subscribe to everything your server load would skyrocket and so would the costs.

      I think it’s much more likely that a better community browser will be incorporated so that people don’t have to rely on third party sites.