3 ms·
I suppose it could be seen as a response in kind after: https://blog.cloudflare.com/dyn-issues-affecting-joint-customers/ https://blog.cloudflare.com/dyn-issues
by cknight 10y ago
I suppose it could be seen as a response in kind after: https://blog.cloudflare.com/dyn-issues-affecting-joint-customers/ https://blog.cloudflare.com/dyn-issues-affecting-joint-custo...
I would consider an email a bit of an escalation though, as opposed to a blog post.
- snug 10y agoThe DYN attack affected Cloudflare customers, and we received a lot of support tickets that day. The blog post was more than warranted. The CEO and managers made sure the sales people weren't scummy in their tactics.
- nicolas_t 10y agoSee the message I received as a Dyn customer... The sales people were scummy in their tactics.
- snug 10y agoI don't think the Cloudflare message is nearly as scummy as the Dyn messaging. Dyn makes it seem like the entire underlying tech at Cloudflare is vulnerable. P.S. I no longer work at Cloudflare, so I don't really care, just my .02
- wyuenho 10y agoIt may not be clear on that blog post, but internally, management stressed on multiple occasions immediately after the dyn incident to "don't be an asshole".
- cknight 10y agoI've made no claim that Cloudflare did anything wrong with that blog post. I can however see how Dyn themselves might not have liked it all that much. And in saying so, I think both the content and medium that Dyn chose in r1ch's post might be further contextualised.