So far for me the process is very convoluted:
- I go to https://browse.feddit.de/ and find the community.
- Then I need to copy it’s name.
- Then I need to go to my particular instance (lemm.ee)
- Then I type manually in my browser address bar lemm.ee/c/<communityname>
- Then I go back to https://browse.feddit.de/ and copy the address of the original instance of the community.
- Then I go back and add the original instance address to already typed thing in step 4 like this lemm.ee/c/<communityname>@<originalinstanceofcommunity>
- 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.
I am not sure why? In the app, all communities that are federated to my server are visible when searching. On desktop, and in the app, all you have to do is select “all” instead of “local” or “subscribed” and then just search. Half the communities I am subbed in are not from my own instance, for example.
Thank you! The search icon was so small on lemm.ee that I didn’t notice. It actually works much better! You’re a saviour!
How do I properly close this thread? Do I have to? Can I mark it as solved somehow?
I think you can edit the title. No rules here, but a simple [solved] should do. Also you are welcome, we are all figuring this out!
Please leave it up. I needed to know this and others will too.
I think it’s a bit harder when you’re on a smaller server. If someone from your server hasn’t subscribed yet I don’t think it shows up like that. In this case, I’ve followed the info in the top right of the webui, and entered !community@example.server into the search, which pulls it correctly.
Correct me if I’m wrong, but that search only exposes the communities that at least one of the servers members is currently subscribed to. It is not a list of all possible communities. This works okay if your server has a lot of members because it will likely surface the main popular communities, but it’s misleading that it’s all communities and someone had to do it the hard way like OP said the first time around.
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?
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.
Aha, fair point!