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.
Note that defederations with smaller instances (representing 12% of users) are not represented here, so there are even more defederations than what is listed here. Hopefully that will come across better with more data in the next version of the graph.
As requiring new users to implement multiple blocks off the bat can be a big ask for those still on the fence about leaving Reddit, defederating known NSFW, troll, and tankie instances can improve new user retention. For those who prefer more hands-off moderation practices, specific instances can cater to them, but I think a more tailored experience is better for users arriving from Reddit.
Idk, that is exactly how lemmy.zip does it. Fairly straight forward if you ask me.
I’m not so sure, I’d rather have a prepopulated blocklist that I can further configure myself, as opposed to instance level blocks that I can’t reverse.
I think the main issue is that this isn’t communicated clearly. Most people joining a random instance listed on join-lemmy.org won’t know what defederation means and they have no way of knowing that by choosing that particular instance they’ll be cut off from a certain number of other users.