1. 8
    1. 10

      A company made some mistake, pissed off user assumes malice and posts their rant to ‘hacker’ ‘news’, and the company ‘makes it right’. Why does this belong on lobste.rs?

      1. 0

        A company made some mistake, pissed off user assumes malice and posts their rant to ‘hacker’ ‘news’, and the company ‘makes it right’. Why does this belong on lobste.rs?

        Did you not read past the erroneous tone disclaimer, or are you just trolling here? Where did Cloudflare make it right? What’s this whole “‘hacker’ ‘news’” in individual quotation marks that you’re referring to? Where did the user assume “malice”? What “mistake” did the company make, when it’s clearly written by the OP that all Cloudflare did was follow its own known policy of not notifying about the nuking of the site of a paying customer, where a simple Google Search query reveals it’s an issue known to the public at large since like two years ago?

        Most importantly, why do you assume malice on part of the victim in this story, and believe Cloudflare the perpetrator, and why do you scorn the victim for doing exactly what Cloudflare told them to do — post the question in public forums, because they’re no longer a priority customer after having had the product they bought removed from their profile?

        The OP has had their whole website and email nuked, potentially lost a lucrative contract with a client (10k USD+?), at the very least potentially lost several days worth of billable time (at kilobuck per day?), and here the tone-police are telling him he’s too quick to assume bad faith (???) on Cloudflare’s part when Cloudflare’s CTO chimed in for damage control, empty-saying they’re “investigating”? (As their CTO always does on HN, BTW.)

        Note that Cloudflare’s CTO still never disputed nor apologised for Cloudflare’s blackbox policy of nuking your whole DNS without any notification (email or otherwise). This is probably the biggest complaint by the user, that Cloudflare didn’t even bother to tell him about this intentional takedown on Cloudflare’s part. It’s been almost a day now, with no updates; will Cloudflare be making it right by reimbursing the OP for the lost opportunities? Or is the victim supposed to issue a full official apology for being a victim of this awesome registrar with such a great CTO that’s “investigating” all issues that hit the media?

      2. 0

        So you can complain about it =)