That’s a known bug in Jerboa. It’s already been reported and the dev acknowledged it.

The best way is to use relative links, such as !technology@beehaw.org

What I did there was simply [!technology@beehaw.org](/c/technology@beehaw.org). This link doesn’t start with the protocol and site, but instead assumes the current site, and starts with /c/my_comunity@my_site.tld, meaning it will be routed to the same instance.

This will probably not work for those on Kbin, since their communities (magazines) don’t start with /c/, but rather with /m/. If anyone knows a good way for this to work for both, I’d be glad to adopt that myself going forward.

That’s because they don’t exist. It’s only a concept rendering. This site spotlights design ideas and their creators, not actual products.

That sounds like an annoying bug. Hopefully since it’s well understood what exactly flipped in the database and how to fix the problem once it happens, the code fix won’t take long.

It’s not that Lemmy is defederating, it’s that Beehaw is choosing to block sh.itjust.works and Lemmy.world, which means those two are no longer able to federate to Beehaw, and vice-versa. So to that end, they’re defederating. Beehaw will keep federating content to other instances (like how I read this from FMHY, and am commenting from FMHY, which you can read).

Hopefully that helps