There’s never a lack of teachable moments, is there between the constant struggles and now this? There’s a difference I think between a teachable one and a totally and completely preventable one. Agree to disagree, I suppose.
If you were asking me personally it’s because I don’t really care. I love the people there but we have weathered worse storms in the past. All the people I care about just hang out in other spaces instead.
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.
There’s never a lack of teachable moments, is there between the constant struggles and now this? There’s a difference I think between a teachable one and a totally and completely preventable one. Agree to disagree, I suppose.
I don’t really see how this was a completely preventable issue. The person who owns the domain said they would keep it up, then they didn’t.
From what I was told the person was hard to get a hold of. Why didn’t anyone start asking questions when that first started occuring?
If you were asking me personally it’s because I don’t really care. I love the people there but we have weathered worse storms in the past. All the people I care about just hang out in other spaces instead.
There is no worse storm than site admins enabling cyberattacks on comrades… not even close. This isn’t “should we stack rocks”
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.