I’m running the Lemmy Community Seeder script on our instance to prepopulate some additional communities. This is causing some sporadic json errors on the account I’m using with the script, but hopefully isn’t impacting anyone else. Let me know if it is and I’ll halt it and schedule for late-night runs only or something.

Right now I have it watching the following instances, grabbing the top 30 communities of the day on each scan.

REMOTE_INSTANCES: '[
        "lemmy.world",
        "lemmy.ml",
        "sh.itjust.works",
        "lemmy.one",
        "lemmynsfw.com",
        "lemmy.fmhy.ml",
        "lemm.ee",
        "lemmy.dbzer0.com",
        "programming.dev",
        "vlemmy.net",
        "mander.xyz",
        "reddthat.com",
        "iusearchlinux.fyi",
        "discuss.online",
        "startrek.website",
        "lemmy.ca",
        "dormi.zone"]'

I may increase this beyond 30 communities per instance, and can add any other domains y’all want. This will hopefully make /All a bit more active for us. We’ve got plenty of storage available so this seems like a good way to make it a tad easier for everyone to discover new communities.

Also, just a reminder that I do have defed.lemmy.tf up and running to mirror some subreddits. Feel free to sign up and post on defed.lemmy.tf/c/requests2 with a post title of r/SUBREDDITNAME to have it automatically mirror new posts in a particular sub. Eventually I will federate that instance to lemmy.tf, but only after I’m done with the big historical imports from the reddit_archive user.