After search wouldn’t show a bunch of communities, I started manually just editing the URLs and then I ran into a new set of problems.
If I go direct to the lemmy instances they work, but via this instance, I’m getting a bunch of 404s.
The list
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
- https://u.fail/c/[email protected]
Apologies, for some reason I seem to be finding all the bugs.
If you do it this way, there should probably be no (necessary) request from your instance to the remote instance.
If no one has done it before, the explicit call via addressing [email protected] using the search field should be without alternative.
Then I’m perplexed. I’m searching and they’re not coming up and I’m using the URL and they’re not coming up either.
I’ve just done a search for !ufail[email protected] and now posting this.
I can find this from my beehaw, I just can’t find a bunch of things and some of my communities aren’t federating
At least with Lemmy I am familiar with the problem situation that the search always outputs after 2-3 seconds that the community does not exist. If I start the same explicit search with the handle again 30 seconds later, it always shows up.
But in the end, this is all just a bit of theory as to whether the problems between lemmy instances are the same as those from kbin to a foreign lemmy instance. So I’m just guessing, sorry.
No worries, I think we’re all pretty much red shirt enterprise officers right now. We’re trying to boldly go where no one has gone before but ultimately we’ll be lucky if we can stay alive. 😂