But widespread layoffs, hiring freezes and resignations have shrunk the number of qualified scientists who can assist state labs. The C.D.C.’s rabies and pox virus teams have lost many of their members. By July, the rabies team will be down to just one person with the clinical expertise to advise state and local officials, and the pox virus team will have none.
deploy and do what exactly? Get involved and potentially sacrifice a few UK soldiers to stroke Trumps ego? Sit around and look pretty? Having a carrier there doesn't magically make problems go away.
The CDN/content provider ships servers to the ISP which puts them into their network. The provider is just providing connectivity and not involved on a content-level, so no MITM etc needed.
Not wrong, but that comes with promoting yourself on ideology grounds. If you want support because you are the plucky underdog community project that cares about people and are running ad campaigns how you are not evil big tech, then don't be surprised if people hold you to it. Mozilla is in this weird space where it wants to be both the good little guys and a proper Silicon Valley tech company, and those don't necessarily mix well.
It's a community matter posted in a public place, a non-statement with an immediate attempt to direct it to private conversation reads like trying to avoid attention to your mistakes (e.g. hypothetically you don't have to public admit you didn't do anything to check for guidelines to follow). More vibe-y, it all sounds very corporate, like any PR statement in response to criticism ever, or a manager writing to an employee in a big corp, not "humans working together in a community, and one of the humans is clearly pissed off right now".
Also while it's phrased as a question, it doesn't offer any alternative next step. So a better approach would be writing down the initial questions you have and then offer that you'd be open for a call if the OP prefers that. If they don't, they can immediately engage with your questions, and they are open to everybody else in the community. Whereas right now if they say "no, I don't want to call you" that's all you've given them.
(To be clear I can easily believe the writer of the response is not intending any of that and means well, but that's how it comes across)
Or answer being clear about that if you feel like you need to respond now. Acknowledge there is a problem, say you'll have to look into the details before you can say more, come back with specific questions if you need answers.
If the post gave any acknowledgement to the already stated complaints I'd agree with you, but it does not, and that does stand out and leads to my reading.
Then say so if someone complains about it? "Shoot, we accidentally ran it in the wrong mode, sorry about that, I'll look into someone fixing it ASAP" is a lot better than "We're sorry for how you feel".
Then at least try to sound like a genuine human that cares and not a PR response when reaching out. Offer a "you can call me if you want" vs making the call the expectation (it's phrased as a question but there is no other path offered).
a) don't apologize for the other persons feelings, but for your actions that lead to it
b) don't look like you are trying to take the conversation out of the community space it's happening in and/or hiding details by going to a private call (you can offer a call, but it shouldn't be the expectation)
c) Acknowledge the concrete complaints made. Are you truly "struggling to understand" what someone means when they complain that it didn't happen in a staging environment first?
d) a-c also lead to "don't sound like any cookie-cutter PR response to a complaint ever, people have learned those are not genuine". Especially if you are a project that makes a big deal out of its community interacting with said community.
e) ideally announce some concrete first step, e.g. pausing the bot
And some of us did upgrade and would like to see the software improve further and buy further upgrades making it even better in the future, but now I expect it'll be turned into a subscription or shut down in the next few years, because its a minor side thing for Canva, and that's sad.
If you try to make ISPs pay for connecting to you, don't expect your users to have a good time reaching your services. And it's difficult to have a "frictionless" popular service if your websites are the slowest ones around.
To the contrary, the big sites want the opposite: they want all users to have as good connections to them as possible, which they achieve by being nice to ISPs.