On my main (@[email protected]), I moderate [email protected]. I thought I’d kinda federate my existence on the platform by creating this alt on lemmy.ml, but when I search communities, while I can find some other lemmy.world ones (validating that .ml/.world federation is working as I understand it), technicaldeathmetal isn’t found. Am I doing something dumb as a user? As a mod? Have I misunderstood the intent of this instance, and I’d be better off trying the same thing from elsewhere? TIA

    • TotallyNotChoco617@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Thanks for helping!

      • I tried exactly that search
      • Other lemmy.world communities (e.g. [email protected], [email protected]) don’t seem to need any special searching syntax
      • I created the community 2 weeks ago

      Any ideas?

      Edit: you can see in the auto-links in our comments, my community returns “couldnt_find_community”, my counterexamples both work fine.

        • TotallyNotChoco617@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Yep - tried in Memmy for iOS and also Firefox (mobile). Glad it’s not something obvious at least! Guess I’ll try again in a while, see if maybe my account’s age is the issue. Thanks again!

          • phoenix591@lemmy.phoenix591.com
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            actually, it looks like theres some issue keeping lemmy.world federating properly with lemmy.ml atm. I saw another post mentioning it and checked myself.

            https://lemmy.ml/c/[email protected] shows the most recent post as 2 days ago when there was really a post around 4 hours ago.

            that’d certainly keep new lemmy.world communities from getting pulled in.

            neither server has defederated with the other, so don’t expect it to be a permanent issue