News for hackers. Stuff that matters.
Re:Namecheap live chat social engineering leads to loss of 2... by swanson on Tuesday April 12, 2016 @04:45PM (#11483425)
Formula:

* Actually apologize in a human way

* Show empathy by identifying the impact of what happened to customers (not your impact internally)

* State action items that you've created, even if they are just in 'evaluation' state

* Indicate that the specific incident in question is being handled outside of this forum

* Take responsibility for things even if you shouldn't "have to"

Re:Namecheap live chat social engineering leads to loss of 2... by voltagex_ on Wednesday April 13, 2016 @12:40AM (#11485781)
For a "what not to do", have a look how (the CEO of?) FTDI responded after they were caught intentionally "bricking" chips that were detected as counterfeit by the Windows drivers.
Re:Namecheap live chat social engineering leads to loss of 2... by Namidairo on Wednesday April 13, 2016 @04:59AM (#11486746)
Last I heard, these tainted drivers from FTDI weasled their way through WHQL and into Windows Update...