Oh, yep, you're right. As I stopgap, if you'd like, I can crosspost for you, so at least you can watch for answers at !ece@lemmy.world in a browser. Just let me know if I should do that.
Ah, it's because nobody on your instance is currently involved in that community, so it hasn't been federated to Beehaw yet. To fix that, go to the search tool, make sure that you have "All" selected for all four filters, and enter "https://lemmy.world/c/ece". If you get a community result, you can click on it and subscribe to the community and then crossposting should work. If you get too many results, try switching the scope from "All" to "Local". If you get no results, it means that federation is pending but delayed. Give it a minute or two and try the search again; eventually the community should show up.
Since you found this sacred knowledge, it would probably be a good idea to comment on the GitHub issue in addition to here, since that's where most people will be looking if they get these errors.
Update courtesy of @chaorace@lemmy.sdf.org: kbin.social has enabled DDOS protections that "may cause some issues with the federation". They will return to normal operation when possible.
No worries. My post hasn't gotten a clear answer yet either, except for suspicions that it's issues with load . I just wanted to make sure that if someone does figure out the issue, we get everyone who is asking filled in.
AFAIK, that's supposed to work, but it doesn't for me either. Question raised here. We'll see what people say.
(My instance does federate with the kbin instance for the magazine I tried to search for, so the problem must be something else. It looks like your instance federates with kbin.social
at least.)
Sentence added to the second-to-last paragraph. Let me know if it looks okay or it you think it could use some edits.
(AFAIK, this is not something that varies by instance.)
Thanks so much! I'm glad it's turning out to be useful, and I'm glad there are people like you staying on top of all those questions.
Got it. The federation was lagging, so I hadn't seen that reply yet. Best of luck!