I thought the point of a fediverse was distribution making it so that no one site becomes death star sized. If one site has ALL the biggest communities… What happens if that site goes down? Shouldn’t each site that wants one have a “Tech” community, and then those get aggregated into Tech? Wouldn’t that be a better approach? Doesn’t it make more sense that no one site has so many users the server can’t handle the load (been waiting for over a week for subscriptions on lemmy.ml to complete). Before someone feels the need to explain to me what they think a federation is, I’ve taught the subject. The point I’m trying to make is… Why do we keep pretending that being the biggest is a benefit, when it is directly detrimental to the architecture that we are using? #justanotheridiot #whatdontiget #federationday

P.S. before anybody goes out of their way to be offended, my hash tags are an attempt at self deprecating humor.

  • @[email protected]
    link
    fedilink
    English
    2
    edit-2
    1 year ago

    It would definitely be ideal for bigger communities to evenly distribute between instances (at least instances hosted on powerful hardware). That would allow us to spread out the load over the network far more efficiently, and it would also give the network much more resilience against a single big instance going down.

    Note that by evenly distributing, I don’t mean that we should be duplicating communities. I am a big fan of users from different instances teaming up and creating cohesive communities with a clear focus! I just think that this works even better if these strong communities are not all crammed into 1-2 major instances.

    • MrEUserOP
      link
      fedilink
      English
      11 year ago

      Just wanted to make sure I wasn’t up in the night.