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.

  • wonderingwanderer@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 hours ago

    If you want to put it that way, you could also argue that anything posted on the threadiverse, or even more broadly, on the internet, is meaningless attention seeking.

    Or you could recognize that we need more content on the threadiverse to get more people engaged to reach the critical mass where we have a network effect which encourages more organic engagement, so anybody posting is doing their part to contribute to a greater cause.

    If they set up a comm with a bot to repost the top three posts a day from a specific reddit comm, what’s the problem? Depending on the instance, maybe the admins don’t want to host that and view it as bloat. They can make their own rules. But on an instance that allows it, or on someone’s own instance, what’s the problem?

    If someone doesn’t want to see it, they can block the comm. If nobody upvotes it, it won’t clog the all feed. If nobody comments on it, what’s the issue if it just sits there and stays empty?