There's a clear lack of communication. The engineering process is (was?) opaque. It's not clear the Go team acknowledged there was a problem with the proxy itse

There's a clear lack of communication. The engineering process is (was?) opaque. It's not clear the Go team acknowledged there was a problem with the proxy itself and not just upstream sources, it wasn't communicated that a fix was being worked on, it wasn't clear when it was due to get out. From the outside you can just wait and hope. But that's not OK when your server is getting hammered 24/7 and you have to pay the bills. Only because DeVault complained do we see that things were happening. Information, but still no control. It's only when DeVault started to actually annoy Google with real visibility that they decided to take responsibility for what they were doing. There's an interesting analogy to class struggle, where DeVault uses his leveraging power of striking to make the big Kapitalist change their ways and assume responsibility of asking too much to the little hands doing the actual work of hosting.