https://aussie.zone/c/[email protected] ostensibly exists. Searching for the specific community [email protected] on my home instance shows “no results” and trying to access the full URL gives me “404: couldnt_find_community”. I’m not exactly sure what to do to get it “federated over to aussie.zone”. Need help.
Search the full url
https://lemmy.ml/c/mangain the search box on aussie.zone and it should come up. If it doesn’t the first time, search again and it should.When it doesn’t show the first time I bet it’ll show zero subscribers. That just means that you’re the first person from aussie.zone to connect to that community. As the first person, you’ll be the one to “pull” it into your instance. This will link it so others can find it just by searching
mangain the future.Edit: for anyone else seeing this. The nature of this really hinders discovery. So that’s why I use lemmyverse.net for global search.
Sorry, but another question. Is it normal that I can’t see old replies?
This is how I see https://aussie.zone/c/[email protected]:
But this is how the same post appears on https://lemmy.ml/c/manga:
I believe this is a cross Instance sync issue that is affecting many communities. BE (back end) update 0.18 is coming with some major changes and the rollout is tomorrow.
OR…this could be that if you were the first to pull the community into the aussie.zone instance that only content/comments from this point forward will be synced. I read that somewhere. Instances must pull community info. They aren’t pushed. Now that you have linked them, they should stay synced (in theory)
Ah I see, that makes sense and that worked. The community also showed up in the search results as a single line that wasn’t very prominent.
The comments containing “https://lemmy.ml/c/manga” were more obvious.
Really need to have the search results delineated by category. Especially since the search defaults to “all”.
Yeah, there is an option to filter your search by community. That helps filter out the tiny community line among all the posts.