I really like the Lemmy Community Browser at browse.feddit.de for locating communities across instances.

When I first stood up my instance, I guess it was crawled and my community showed up there. Awesome!

I’ve since rebuilt on a new domain and federated again, and my old instance dropped off (as expected). However, a day or so later, my new instance still isn’t showing up there. The new instance is known to join-lemmy.org and fediverse.observer, so it is discoverable.

I’m curious if anyone knows how often it updates and if that tool is based on a project I can clone to spin up another instance. I’m interested in both running a replica of it to act as another entry point as well as using it as a base to develop some quality of life enhancements. e.g. a click to subscribe option that ties into your home instance and does the initial search and subscribe steps.

  • @wintermute@feddit.deEnglish
    4•11 months ago

    So it may be possible my instance was rate-limiting the crawl which contributed to that?

    might be an option.
    and the more instances link to yours, the more likely it will be crawled, in case other instances drop out.

    i 'd have to update the repo at codeberg, but right now it has low prio for me as i broke my hand and try to stay away from the keyboard ^^

    • Admiral PatrickOPEnglish
      3•11 months ago

      and the more instances link to yours, the more likely it will be crawled, in case other instances drop out.

      I’ve got a lot of peers in my instances list (lemmy.ml, beehaw.org, feddit.de are the largest peers), and I’ve clicked into the /instances page of many of them; they all show my domain as a peer, so I believe I’m good there.

      but right now it has low prio for me as i broke my hand and try to stay away from the keyboard

      Well, I definitely thank you for powering through to answer my dumb questions, and I do appreciate your time.

          • Admiral PatrickOPEnglish
            2•11 months ago

            There it is!

            Thanks for checking back.

            I want to say the blame lies 100% with me on this one.

            When i moved over to the new domain, I forgot to disable my default WAF policy for robots.txt which is set to disallow all. Realized that late yesterday evening and turned that rule off in my load balancer.