I was trying to access [email protected] through beehaw as it seems to be the largest related community currently, and I can’t seem to access it, I just get a 404. I am able to access other communities on that instance, but not this one. Is it considered NSFW and thus blocked?

edit: working now. Tried it earlier and then tried again a few hours later and it was still not working. Looks like the solution is searching via beehaw itself with the full community address. going there via URL doesn’t work to make beehaw recognize it.

    • GhostMagician@beehaw.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 year ago

      I hope something that automates the process of subscribing and interacting with communities in other instances comes out so the @ blah blah portion stops being necessary to manually input.

      • towerful@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        The @ denotes the instance tho.
        There could be a trees community on 3 different instances, 1 for weed, 1 for actual trees, 1 about binary searching.
        So, I don’t think it’s going away any time soon

  • ABlackWaltz@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I think it’s just how the different instances interact. If you click the search icon (spyglass) to the left of your name and enter “[email protected]” and click search, you should see this post and the community you’re looking for. Sometimes you have to search and then wait for the beehaw instance to pull the information in order for the community to show up, so give it a few minutes and try again if you search for a different community and don’t see anything.

    • Boe6@beehaw.orgOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      ^ This is it. I was attempting to go there by typing the URL directly, not via searching. I’ve been able to get to a couple more via this method now, thanks!