Skip Navigation
Lemmy @lemmy.ml maltfield @lemmy.ml

Comparison of Lemmy Instances

github.com GitHub - maltfield/awesome-lemmy-instances: Comparison of different Lemmy Instances

Comparison of different Lemmy Instances. Contribute to maltfield/awesome-lemmy-instances development by creating an account on GitHub.

GitHub - maltfield/awesome-lemmy-instances: Comparison of different 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 :)

120

You're viewing a single thread.

120 comments

  • 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.

120 comments