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:

  • blackn1ght@feddit.ukEnglish
    1·
    4 months ago

    The problem is most likely people that are new to the fediverse/lemmy just not understanding it and choosing a “default”, popular instance. I was going to pick it as a safe option when I first came here but it was under load and wasn’t accepting new users, where I then had to find another instance and settled on feddit.uk.

    It would be good if lemmy instances could have the option of “load balancing” new users, so if the current instance has way more active users than it’s federated wtih then it disables registration but recommends other, smaller instances to the user.

    • ngwoo@lemmy.worldEnglish
      3·
      4 months ago

      We just need a way to make it easy to seamlessly transfer both users and communities to another instance then it really won’t matter if one gets disproportionately large because a shutdown won’t affect anything. Ideally the inner workings should be as invisible to the end user as possible.