I’ve noticed that communities from sopuli.xyz aren’t showing up in the search. Is Pawb.Social having issues federating with that instance? Or is it just that the instance might be overloaded?
I’ve noticed that communities from sopuli.xyz aren’t showing up in the search. Is Pawb.Social having issues federating with that instance? Or is it just that the instance might be overloaded?
Searching is a bit odd, I’ve found. You’ll need to search for what you’re looking for first - if no one else has before searched it on your instance, it won’t show up the first time, but it’ll prompt the instance to search for it.
The next time you search for it (give it a minute or so) , it should show up unless it’s not federated from my understanding.
I did end up getting it to work. It’s a bit buggy I had to try again several times for some of them, or wait like 5-10 minutes before trying again.
Basically, from what I’ve gathered, if you’re the first user to try and talk with that community/instance from this one, you need to do an external search, i.e. !communityname@instance.site
Give it about 30 seconds to a minute for the servers to link up, and our instance will grab that community’s info and their top 20 posts to populate. Then you can just search it by its community name and it’ll show up to subscribe. Once you sub to it, it’ll formally federate and pawb.social will start downloading posts from that community regularly.
It’ll be up to us early users to build the connections for later folks to use.
Wow, that makes so much more sense. It would be nice if the UI made that behavior clear, as just returning 404 errors generally means “this does not exist”, not “I might need to take a second to look for this”.