Skip Navigation

Comparison of Lemmy Instances

I created a repo on GitHub that has a table comparing all the known lemmy instances

Why?

When I joined lemmy, I had to join a few different instances before I realized that:

  1. Some instances didn't allow you to create new communities
  2. Some instances were setup with an allowlist so that you couldn't subscribe/participate with communities on (most) other instances
  3. Some instances disabled important features like downvotes
  4. Some instances have profanity filters or don't allow NSFW content

I couldn't find an easy way to see how each instance was configured, so I used lemmy-stats-crawler and GitHub actions to discover all the Lemmy Instances, query their API, and dump the information into a data table for quick at-a-glance comparison.

I hope this helps others with a smooth migration to lemmy. Enjoy :)

93 comments
  • Users can create communities on Blahaj Lemmy. Most of our communities are created by users

    • Hmm, I see community_creation_admin_only is set to false on the API. I'll look into this, thanks for letting me know :)

      Edit: should be fixed now. Please let me know if you find any other issues :)

      • Same for lemmy.studio, I have community creation open for everyone. Not sure why it shows as false.

        What's the API endpoint? I'll double toggle the option to see if it fixes it, maybe it is set to admin only even if the UI shows the opposite.

  • I also recently just created my instance vlemmy.net, I dont mind anyone joining and creating their community's there. Dont really have any restrictions either. Would be nice to learn some new things from our internet friends

  • How do you check wether nsfw content is allowed?

    Because my instance (feddit.de) doesn‘t allow pornographic material. I guess that doesn‘t exclude all nsfw content. But the column header is called adult and it makes it seem like „adult content“ aka porn was allowed.

    *edit fixed typo

    • It doesn't say porn, it says adult. The legend describes how it's determined

      Adult "Yes" means there's no profanity filters or blocking of NSFW content. "No" means that there are profanity filters or NSFW content is not allowed.

  • It would probably be useful, but harder to collect, a summary of:

    • Primary/intended topics or users (eg, tech, politics, regional, etc)
    • Any unusual moderation patterns
    • Most/least blocked
  • are manual additions allowed? our host's security blocks some bot traffic and is currently not playing nicely with the stats crawler

    • Manually maintaining is not realistic.

      If your API is read-only and you're blocking bot traffic from querying it, you're doing it wrong. Please be nice to the bots. And also users that use VPNs, privacy plugins, etc. You'll false-positive block them, and that's not very nice.

      • definitely agree. I don't control our host's policy but i will pass that along. some bot traffic is allowed- we were on the join-lemmy site two days ago and i have a bot running this very minute- i think they're still just trying to dial in the right balance between two much and not enough security

  • The new user registration doesn't map to the recommended setting of admin approval only. There have been massive spam account registrations waves in the past and if you can't monitor your instance 24/7 this is the only way to prevent having your instance blocked because of that.

    • The NU field is determined by checking the registration_mode field in the API. If that's set to closed then I say No. Otherwise, I mark it as Yes.

      So if it's open or require_application, I list it as Yes.

      Is there an issue with how I've set this up? If so, please name a specific instance and what it should say vs what the table says.

93 comments