I’ve seen this mentioned a few times already: people wondering why certain communities don’t show up in their instance. You need to first search for that community via the magnifying glass icon and type in “!communityname@instance.domain”
Notice the exclamation mark at the beginning. Might take a few seconds. This will teach your instance about the remote community.
I believe the devs have said they’re working on making that work more automatically. Like having it happen as soon as a user clicks a link to it for the first time on your server. And also making links to communities outside your home instance automatically be changed so that it keeps you on your instance where you’re logged in.
For example right now if someone on BeeHaw.org clicks https://lemmy.ml/c/memes, it’ll take them to lemmy.ml where they’re not logged in. They should add /c/ tags like /r/ on reddit, and when someone on BeeHaw clicks something like /c/memes@lemmy.ml, it should take them to beehaw.org/c/memes@lemmy.ml so they can stay signed in and comment/vote/post. You can do this manually right now by creating a link like so:
Any idea if there is a delay in community searching? Someone mentioned a newly created community (1 hour ago) on sh.itjust.works and I searched on lemmy.world for it and nothing but I can visit it directly.
Not really. There shouldn’t be a delay at all. If it doesn’t work something is broken down or you aren’t using the correct syntax
Make sure you search on ALL (not just communities) and write it like !name@sh.itjust.works
We need a way to search across servers for a community
Try this: https://browse.feddit.de/
I’ll agree that fetching a new community is much more awkward than it should be.
This didn’t work for me on this instance. Can some communities choose not to participate or limit their import? I searched for !aviation@lemmy.ml and several others and nada.
This has been changed with the latest version of Lemmy. Try this link: /c/aviation@lemmy.ml and check over at lemmy.ml/instances to make sure your instance is not blocked. (It’s at the very bottom, I just checked for you and it doesn’t look like it).
Edit: your instance is using an older version. Searching should still work. Try a couple of times. Make sure the search page is /search and use no filters
