What the title says. I think there is still a long way for that to happen but i’ve been hopeful. What do you think?

  • speaker_hat
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    That is a (good) question every venture ask. Eventually everything scales, and I have a feeling that it won’t be an issue.

    • Shikadi@wirebase.org
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      While you’re probably right, I would like to know how it’s going to be handled on a technical level. I would imagine the protocol has to already have support for something along those lines, but I’m too lazy to go look and understand for myself. Maybe in a week or two if I don’t know it I’ll start looking at the sauce code

      • jochem@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Nope, ActivityPub (the protocol) doesn’t support communities to be distributed over multiple instances.

        Instances can horizontally scale to multiple servers, just like massive websites like reddit do. If you host a huge community, you can gather enough donations to pay for the hosting of your scaled instance.

        I can imagine that a future version of ActivityPub will support something like grouping communities of different instances, which could also allow scaling, but will be a bit awkward given you’d then have a community run on multiple instances, so with potentially different rules and the possibility of communities splitting when the instances decide not to group or federate anymore.

    • henfredemars@infosec.pub
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      The hope is that it scales upwards!

      Or eventually, it scales the other way when someone else who can scale better than you comes along, at least in the world of social.