- cross-posted to:
- lemmy@lemmy.ml
- cross-posted to:
- lemmy@lemmy.ml
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
allowlist
so 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 :)
Great work! Thanks for making this. ❤
@maltfield
It’s cool seeing this post in Mastodon.There is also a similar list on: https://the-federation.info/platform/73
oh shit I wish I knew that existed before XD
@maltfield So apparently I can interact with my Lemmy posts on my Mastodon account. Cool!
For anyone else trying to figure out how: I just took the URL of the Lemmy post (https://lemmy.ml/post/1168743) and pasted it into the Mastodon search field.
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 be nice for those elsewhere on the fediverse to know when an instance is aligned with or run by the same people as an existing mastodon or other kind of instance.
Pretty sure nothing conventional is exposed for that sort of information, but it could be useful in the future. Maybe a general description field that can contain that sort of information.
How about a spreadsheet release (on GitHub) so we can easily filter things out? 👀
expired
Users can create communities on Blahaj Lemmy. Most of our communities are created by users
You’re awesome man! This is direly needed. I’m just wondering how on earth to publicize this before the madness that hits on Monday.
Any chance you could find a place to fit this in the join lemmy site and do a pull request before then? I know it’s a lot to ask, but it would be huge.
I see TypeScript and get scared. Personally, I do think that the join-lemmy.org/instances page should link to:
- My table comparison https://github.com/maltfield/awesome-lemmy-instances
- The Lemmy Community Browser (to find communities across all instances) https://browse.feddit.de/
- The Lemmy Map https://lemmymap.feddit.de/
- The federation’s lemmy page (with another table comparing instances) https://the-federation.info/platform/73
Can anyone with TypeScript experience make this PR for us? Here’s the relevant file:
You thinking just a <ul> with the 4 links in it and a header of some sort? Mock or description or anything?
I think at the top, just above the “Recommended” <h2> add:
For a more detailed comparison of Lemmy instances, see: <ul> <li><a href="https://github.com/maltfield/awesome-lemmy-instances">Awesome-Lemmy-Instances on GitHub</a></li> <li><a href="https://the-federation.info/platform/73">the-federation.info Lemmy Instances Page</a></li> <li><a href="https://lemmymap.feddit.de/">Feddit's Lemmymap</a></li> </ul> After you create an account, you can find communites across all instances using <a href="https://browse.feddit.de/">Feddit's Lemmy Community Browser</a> <h2>Recommended</h2> ...
Removed by mod
Instances aren’t added manually. They’re discovered using lemmy-stats-crawler.
As long as your instance is federating, active, and the API is reachable then it will make it onto the list.
Edit: It looks like your instance’s API isn’t reachable, which may be why it’s missing:
Please fix the availability of your instance’s API.
hexbear is currently running an old version of lemmy that doesn’t support the v3 API or federation. migration to a more modern lemmy is in progress
About 300 active users every day
Underselling it? 431 currently logged in at time of this comment and it hits 600 concurrently logged in at peak time basically every day. The statistic this repo uses is also:
**Users ** The number of users that have been active on this instance this month
By that metric I think Hexbear is still the largest lemmy instance. It would be the third on this list if you only count daily concurrent login peak.
Removed by mod
I see, so it’s commenting accounts per hour. Would be interesting to see what the commenting accounts per month is to more accurately compare to this list. Although this list doesn’t make it clear whether they are using accounts that have commented or accounts that have simply participated via logging in and voting, I would personally include any voting account as “active”.
Removed by mod
Only wish we knew what the definition of “active” being used was more clearly.
the lemmy source code is public
I mean in this git. “Active” is at the entire discretion of the person that made this list and is not quite fully defined.
I’m a little bit confused by the federation thing. How would I let my instance talk to any other instance except the ones I blacklist?
It’s documented here:
By default users on an instance will be able to talk with communities/users on all other instances. This only changes if the instance admin puts hosts in the
allowed
list or disables federation.If you add instances to the
blocked
list then users will be able to talk with all other instances, except those on theblocked
listOh I see. I had put Lemmy.ml on the allowed list and never intended other instanced to not be allowed.
Fixed, thank you!
It says i can’t downvote on beehaw , but going to this (beehaw community post) and downvoting workds.
Does this mean that Beehaw users can’t downvote on any other instances whereas users from other instances can downvote Beehaw content?
I read that they just ignore incoming downvotes, so on Beehaw you’d never see them, only locally on the instance where you voted.
That would be the proper way to implement this, but I can confirm that I’m able to downvote Beehaw content from this instance, it shows my downvote and the vote count decrements by one. Maybe it’s just a caching thing.