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.

Maybe also crosspost to !ece@lemmy.world, which should be good at helping out with such questions?

I wish, but lemmy.blahaj.zone is not mine, just one of the larger medium-sized instances that have been around for a while. But some people do do as you describe.

I see—you’re talking about instances with no users? Yes, those don’t help much. Maybe edit the typo “a significant piece of auditory” in the original post, since I guessed that you were talking about instances with users but no communities.

Every server just has a cache … there is no profit for the whole network …

I wouldn’t say that caching is no profit. Yesterday there were several times when lemmy.ml was struggling or effectively down for some people, but despite complaints over there I could read lemmy.ml communities just fine through my instance. Caching meant that I was isolated from the service interruption, and the lemmy.ml server was isolated from my contribution to its load.