I have a number of Lemmy instances meant for discussion groups around specific topics. They are not being as used as I expected/hoped. I would like to set them up in a way that they can be owned by a consortium of different admins so that they are collectively owned. My only requirement: these instances should remain closed for registrations and used only to create communities.

  • rglullis@communick.newsOP
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    2 hours ago

    Dear Lord, I had no idea one could be so lost and still be so confident when making an argument.

    I am not trying to be mean, it’s just that you are arguing against things that are completely made up.

    So instead of one admin being able to take it all down we have multiple

    Shared ownership is a policy to prevent single-points-of-failure. Every large-ish instance has multiple admins. This is even a requirement in the Mastodon Covenant: your instance is only listed on the joinmastodon site if the instance has at least two people who can independently access the admin panel.

    Could go and notarize shared ownership of a bare metal server I suppose?

    You don’t need any of that. As long as the collective has control over the domains and that backups are created and available for everyone, admins could simply move the instance to a new place with a new deployment and a DNS change.

    It does not mean that every admin needs to have direct access to the server, and it does not mean that the server will go down if one of them goes rogue. Every minimally competent organization has security processes in place to avoid that.

    But we have multiple admins, so these instances would be uniquely able to process very large numbers of users on account of having more than one admin?

    I can’t even imagine how you go to this non-sequitur. The idea of having multiple admins is only to ensure that these instances are not under control of a single individual and would not be represent a systemic risk to the overall Fediverse.

    If you want communities to be resistant to server removal

    Another non-sequitur.

    So that even if the original instance is gone, everyone keeps interacting with their local federated community-copy

    How is that working out for the communities on feddit.de, and the many other instances that disappeared in the last year? Did you notice they are gone?

    In particular because that still doesn’t solve the problem because now you got people able to either moderate each others copy

    Another non-sequitur. Are you sure you have a clear understanding of how federation works?

    • Carighan Maconar@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      57 minutes ago

      Ah, sorry if that wasn’t clear, the entire second half was theoretical about a better way of doing this.

      A type of federation where there is no “home” for a community any more. It exists equally on all servers, so any being removed would have ~0 effect.

      I mentioned that basically because I feel that’s a much better solution to the problem than shared ownership + locked registrations. Sorry if that wasn’t clear, not my primary language.

      • rglullis@communick.newsOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        45 minutes ago

        A type of federation where there is no “home” for a community any more.

        This is not federation anymore, but an entirely different architecture. Nostr works like this, but it also has its flaws.

    • Blaze@feddit.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 hours ago

      Are you sure you have a clear understanding of how federation works?

      I’m not sure they do, I was confused by their comment as well.