- cross-posted to:
- lemmy@lemmy.ml
- askbeehaw@beehaw.org
- sdfpubnix@lemmy.sdf.org
- cross-posted to:
- lemmy@lemmy.ml
- askbeehaw@beehaw.org
- sdfpubnix@lemmy.sdf.org
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:
- Some instances didn’t allow you to create new communities
- Some instances were setup with an
allowlistso that you couldn’t subscribe/participate with communities on (most) other instances - Some instances disabled important features like downvotes
- 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 :)
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