Hacker News Reader

Comment by stillicidious | Hacker News Reader

I'm glad commenting on HN takes priority over notifying your enterprise customers.

First, please don't be an asshole and/or be snarky on HN. We don't want that here. (See https://news.ycombinator.com/newsguidelines.html.)

Second, "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith." (also in https://news.ycombinator.com/newsguidelines.html)

Third, punishing users for discussing something work-related is one of the worst things you can do to damage this place. We want knowledgeable comments, and for most people, our work is what we know the most about. Disincentivizing that is a losing proposition (https://hn.algolia.com/?query=disincent%20by:dang&dateRange=...) so please don't.

I'd suggest you are doing far more damage to the reputation of the board by conflating commentary with free marketing. The comment I replied to was the latter. If advertising is permitted where critique from actual paying users is openly punished, what is that saying about the board?

As for the extremely disappointing asshole comment, coming from a moderator is quite frankly astounding. "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith".

We have whole teams of people to get status up and inform people and support them.

And yet I'm learning about this outage from HN. How did that happen?

Suggest subscribing on https://www.cloudflarestatus.com/ as that was updated long before I came to HN to say anything (which was only after the incident was resolved).

Maybe it happened because you're busy commenting on HN instead of checking their status page.

Aviate Navigate Communicate.

They did all three of those in the space of a few minutes (if you were checking their status page - which you can subscribe to by the way).

That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.

> That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.

I agree with you, but Cloudflare seem to have done exactly what you're describing in this instance?

Yes, my comment was about the Aviate Navigate Communicate rule, not about cloudflare's response

Reply on news.ycombinator.com