The biggest surprise for me was the https://hexbear.net count, an instance I hardly interact with.

Community Count Community Subscriber Count
beehaw.org 6 133450
hexbear.net 33 663204
lemdro.id 1 17052
lemmy.blahaj.zone 1 15907
lemmy.dbzer0.com 1 53006
lemmy.ml 14 356460
lemmy.one 1 16257
lemmy.world 39 851950
lemmynsfw.com 2 33586
sh.itjust.works 1 16006
sopuli.xyz 1 14093

The data this is based on comes from https://lemmyverse.net where you can just download a full json of the data they have (I excluded all communities marked as “suspicious”)

EDIT: The data if you sort by active users last month:

Community Count Community Active Month Count
awful.systems 1 2616
feddit.org 2 7363
feddit.uk 2 5289
hexbear.net 1 2952
lemdro.id 1 2898
lemm.ee 3 8898
lemmy.blahaj.zone 1 11422
lemmy.ca 3 14910
lemmy.dbzer0.com 3 13752
lemmy.ml 10 54949
lemmy.world 57 338384
lemmy.wtf 1 3602
lemmy.zip 3 12020
mander.xyz 1 11469
sh.itjust.works 5 37365
slrpnk.net 3 10897
sopuli.xyz 2 10070
ttrpg.network 1 4107

Community Count:

Community Users:

  • ᴇᴍᴘᴇʀᴏʀ 帝A
    link
    fedilink
    English
    arrow-up
    4
    ·
    5 months ago

    Our instance is federated with hexbear, lemmygrad etc. I want to be resonsible for what I see and block, I’m really not a fan of defederation unless it’s a last resort (i.e. CSAM or other illegal content).

    Yes, that’s pretty much our take on it: we’ll defederate CSAM (and nonce-adjacent) instances asap, those with lax registration tend to become havens for spammers and trolls, so there is usually a wave of defederating, then someone reaches out to them, it gets sorted and we allow them back in. That tends to be the regular defederation and isn’t controversial. Defederating, for example, Hexbear over, for example, trolling would be a bigger deal and we’d try and speak to the other Admins about it before any permanent banning.