Beehaw Support - Lemmy.ca
lemmy.ca
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here. A brief FAQ for lurkers and new users can be found here [https://beehaw.org/post/452132]. Our June 2023 financial update is here [https://beehaw.org/post/428209]. For a refresher on our philosophy, see also What is Beehaw? [https://beehaw.org/post/107014], Beehaw is a Community [https://beehaw.org/post/140733], and A few thoughts on Beehaw’s design [https://beehaw.org/post/439918] (second half [https://beehaw.org/comment/84235]).

I’m wondering if this is an issue with this instance, or a deliberate choice by either server operator which communities to federate between lemmy.ca and the other server?

In this case: https://lemmy.ca/c/[email protected] works, https://lemmy.ml/c/[email protected] works but https://lemmy.ca/c/[email protected] gives a 404 error code.

Any advice or available workarounds would be appreciated.> good 5-10 seconds for the result to show up. i believe it needs to query the server and takes a bit sometimes.

E: Answer thanks to smorks: You have to search for the community on lemmy-ui and wait 10 seconds or so for it to appear, then anytime after the community search result is essentially “cached” for everyone on your server and will appear immediately, even within a partial search.

E2: Search for !community_name@lemmy_instance.com in the searchbar, filtering by Communities. If it shows “No results”, try again in 10sec. If it shows nothing or the community then it is discovered and the federated URL (your_instance.com/c/community_name@lemmy_instance.com) should work.

    • @smorksMAEnglish
      2•11 months ago

      see my answer above, if you search for either https://infosec.pub/c/securitynews or !securitynews@infosec.pub, then click on the link that shows up, it should start working.

      • @glandridEnglish
        2•11 months ago

        Awesome, that worked. Thanks Smorks!