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 [email protected]

What I did there was simply [[email protected]](/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.

I, personally, don’t feel that adding friction is the answer. I also opted not to apply to join Beehaw because I think having arbitrary criteria to join is problematic. I like the idea that the mods care so much, but it’s simply unsustainable. That and I don’t believe that creating a bubble of like-minded people is healthy. Having terms of service and a code of conduct is one thing. Having an interview process is unappealing to me, and leads me to wonder how that community has gotten as big as it has. The answer is likely “slow growth”.;

Take that for what you will. I would love to join Beehaw, but refuse to jump through hoops. Frankly, you need me more than I need you. Either you play a part in Lemmy’s growth, or you add so much friction that people choose to walk away. Lemmy’s hard enough already with all the bugs and the half-baked features. Adding more friction will defer newcomers further. Is it a win to deter a potential Lemmy user from adopting the platform?

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

That’s awesome! I was worried about the discoverability of communities given that you need to know not only that a community exists, but WHERE it exists, in order to discover it. That renders search effectively useless for discovery.

I do see a few issues with grouping, such as moderation and ownership issues, but I think that needs to be a feature for this to really be usable.

I like the concept, and so far I like the implementation, but it’s still far too early to gain mass adoption based on what I’m seeing from bugs (account creation silently failed on multiple instances, and login can also silently fail) as well as how registering can feel like jumping through hoops. I wanted to register for beehaw but don’t much care to go through an interview process. Then I wanted to make sure I could access beehaw content, but saw they recently defederated from lemmy.world and sh.itjust.works, so I had to make sure not to register on either of those.

I don’t know this will catch on. Currently each instance is so small, and the communities are even smaller. I worry that content won’t update often enough to warrant checking more than once or twice a day. We’ll have to wait and see how much this all grows and matures. I’d like this to be my Reddit replacement, but we’ll see.