Got it. The federation was lagging, so I hadn’t seen that reply yet. Best of luck!

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 [email protected] 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 [email protected], which should be good at helping out with such questions?

Indeed. egg_irl is also moving there.

Searchable version of the link: https://lemmy.nerdcore.social/c/mahjong

The grey link button takes you to the comment in the same instance as you are currently using.

The rainbow pentagon button takes you to the comment in the hosting instance (which may be the same if you’re browsing a local community).

I don’t know many situations where one would actually click on them—maybe the latter is useful if you’re worried that federation is being slow and you’re not seeing votes or replies through your local instance. But the two links can be useful to copy (by right-clicking, or long-pressing, or whatever you do to copy links in your browser/app), the former if you want to show somebody else what a comment looks like through your home instance and the latter if you want to link to a post/comment normally.

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.