Hello,

I created the community “Japanese Metal” https://sh.itjust.works/c/japanese_metal The problem is, it can’t be found on several other instances. I tried on Lemm.ee and Kbin.social, and both return a “not found”. What’s wrong? Is there anything I can do to fix it?

Thanks in advance.

  • Wander@yiffit.net
    link
    fedilink
    English
    arrow-up
    9
    ·
    2 years ago

    You need to be a user at that instance and write the community in the search box so that it’s discovered and fetched for the first time.

    Type it in as !name@instance.domain

    Search Wait a few seconds Refresh page if still doesn’t show. Then it should appear. Subscribe

    This teaches the remote instance that this community exists.

    • Hanabie@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      2 years ago

      I signed up there and searched the community, didn’t work. Waiting and refreshing also didn’t do anything.

          • JohnnyCanuck@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            3
            ·
            2 years ago

            Okay, I’ve found searching with the full url in the search on the website of the instance you’re trying to see it on works best. So put “https://sh.itjust.works/c/japanese_metal” in the search. Initially you won’t get any results, but after a few minutes searching normally (just the name) will work. I don’t know how long, I usually just put the url search in then “walk away” and check back later.

            You’ve confirmed that those instances are federated with this one? Like, other communities from here show up there?

            • Hanabie@sh.itjust.worksOP
              link
              fedilink
              English
              arrow-up
              3
              ·
              2 years ago

              Yes, both kbin.social and lemm.ee are federated with sh.itjust.works I think it just needs to register once on an instance, which still means it won’t pop up on many others, unless someone specifically searches for it – and why would they do that, if they’re just browsing the community list?

    • Hanabie@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 years ago

      That’s weird, I couldn’t find it on either .ee or kbin. Maybe one of the bugs that’s haunting Lemmy right now.

      • Speff@melly.0x-ia.moe
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 years ago

        Can potentially be slow federation. I only have two people on my instance so it’s not like it’s spending much time doing anything else. I’ll check it out on .ee in a sec if I can make an account. The admin there knows their stuff so I don’t think it’s broken

          • Speff@melly.0x-ia.moe
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 years ago

            Sure thing. I’m seeing a similar result searching on .ee and I also see there’s one subscriber to your community on that instance - looks pretty similar to my screenshot above. If you’re still having issues, there may be some browser wonkyness going on, but either way your community is visible to others.

            • Hanabie@sh.itjust.worksOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 years ago

              I could find it, and I see 0 subscribers, while there are 110 when I look at it using my sh.itjust.works account. Really weird.

  • Faceman🇦🇺@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 years ago

    Gotta force federation for small and new communities by searching for it by the full URL, once it has been federated by one user it is there for anyone on that instance.

    • Hanabie@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 years ago

      Yeah I did that now. Took a few minutes for the server to return a search result. Growing pains :/