I'm mostly talking out a technical solution for community redundancy, similar to setting up redundant VM hosts or more accurately like redundant network hardware, where the data and configurations all exist on both servers, and might be load balanced to some degree between both servers, but ultimately should one go down there's no loss of uptime as the other server takes over until the time that it's mate comes back online or a new one is setup and connected
I'm mostly talking out a technical solution for community redundancy, similar to setting up redundant VM hosts or more accurately like redundant network hardware, where the data and configurations all exist on both servers, and might be load balanced to some degree between both servers, but ultimately should one go down there's no loss of uptime as the other server takes over until the time that it's mate comes back online or a new one is setup and connected
But that's infrastructure redundancy, it should rather happen there than at the Lemmy level, no?