In the graph above I’ve arranged the 28 Threadiverse instances with at least 200 monthly active users (MAU)—orange instances running Lemmy, green Piefed, and red Mbin—on the basis of which instances they defederate.
Each instance has its MAU count listed below it, sourced from the latest MAU figures at Fediverse Observer, with adjustments made to the totals for Piefed (due to undercounting by outdated instances, as noted here; I used @Vicinus@piefed.zip’s suggested estimate of 7,200 Piefed users) and Mbin (due to tardigram.com having a duplicate listing).
After adjustments, there are an estimated 43,287 monthly active Threadiverse users (35,184+7,200+903), of whom 87.84% are on the 28 largest instances. The percentages listed alongside the MAU figures correspond to each instance’s share of the total MAU count.
Defederation data was sourced from Federation Checker. The tool doesn’t support Mbin instances, so I left fedia.io in its own category. If any defederations are missing, feel free to let me know. Ideally such a chart should also include community blocks to better illustrate which instances block what, but that data doesn’t appear to be as easily searchable.
I also noticed cases of some instances being listed as being defederated by another instance, despite not appearing on the defederation list for that instance (i.e. reddthat.com and lemmygrad.ml are listed as being mutually blocked, despite neither having the other on their block lists). In testing that federation, I noticed that !wholesome@reddthat.com did not federate to Lemmygrad while !memes@reddthat.com did, so clarification on that matter would be helpful.
While I’ll update my generalized chart as needed to correct errors, perhaps at some point an automated federation mapping tool similar to the one feddit.de formerly hosted could be developed to more completely illustrate instance federation.
As many instances were already blocking the original lemmynsfw.com, I suspect most do it as a means of moderating the feeds of new users who might not want to see porn. An alternative to this (as mentioned by @Cricket@lemmy.zip) would be blocking access to its communities (versus the instance itself) by default, allowing users to see replies from fedinsfw.app users and unblock the communities should they wish to. In either case, I think user retention is better served by limiting access to such content to those who are specifically interested in it.
For Multiverse and apparently Blahaj specifically, they defederate it over CP concerns due to it hosting a ‘Fautbait’ community.
Makes sense, thanks for the background!
Hey thanks for tagging me, but let me clarify because that’s not exactly what I meant. Lemmy.zip doesn’t block any communities by default (as far as I can recall, at least). It blocks a couple of instances by default, and each user can remove those blocks if they wish. This is different from defederating from those instances because defederation cannot be controlled by users, only by admins, but it’s still an instance block, not community block.
Thanks for the clarification 👍 Clarified with italics that what is being blocked is access to the communities, rather than a direct blocking of individual communities.
The key distinction I wanted to highlight—aside from unblocking being an option—was that users from the blocked instance can still interact with communities on the blocking instance, compared to defederation.
No problem!
I always felt it was strange that it didn’t just happen at the client level. Should have had flags in the initial design and moderate to enforce. Just turn the default off on all clients people can turn it on if they want.
The fautbait stuff is obviously a deeper problem