And it’s been nine days since we learned 0.19.1 didn’t fix the problem. There’s a lesson to be learned here: don’t push a massive update close to the holidays because, ya know, you might break federation and go on vacation for a week+.
And it’s been nine days since we learned 0.19.1 didn’t fix the problem. There’s a lesson to be learned here: don’t push a massive update close to the holidays because, ya know, you might break federation and go on vacation for a week+.
I agree, it’s valid to point out amateurish behavior, like devs releasing a highly anticipated major update that breaks core functionality… Then pushing an emergency “fix” that didn’t actually fix the problem and going radio silent for over a week because it’s the holidays. But sure, we can focus on server admins if you want.
It usually takes multiple mistakes for a failure this big.
It’s not a devs vs admins, this was a failure on both sides. This is early days for the Fediverse, I’d imagine this will shake out over time as unreliable instances are abandoned and we get more devs and they learn to or get what the resources needed for better testing.