It was preventable in the sense that the admin team probably should not have continued relying on a single point of failure who had already shown themselves to be unreliable and prone to vanishing for extended periods, but I think it’s also not really a blameworthy mistake. They assumed good faith in people who had helped to set up the site and pay for the infrastructure, which is understandable. It’s a learning opportunity for sure and very preventable in hindsight, but not really anybody’s fault I don’t think.
Sure, but without a complicated legal entity, “the person who controls the DNS” will always be a single point of failure. Questions maybe should’ve been asked earlier, and backups put in place, but nothing about the issue was preventable.
It was preventable in the sense that the admin team probably should not have continued relying on a single point of failure who had already shown themselves to be unreliable and prone to vanishing for extended periods, but I think it’s also not really a blameworthy mistake. They assumed good faith in people who had helped to set up the site and pay for the infrastructure, which is understandable. It’s a learning opportunity for sure and very preventable in hindsight, but not really anybody’s fault I don’t think.
Sure, but without a complicated legal entity, “the person who controls the DNS” will always be a single point of failure. Questions maybe should’ve been asked earlier, and backups put in place, but nothing about the issue was preventable.