2 ms·
As much as the actual cause of the concern (apparently serious employee error) was preventable, I was still impressed by their detailed disclosure, the steps th
by aroman 13y ago
As much as the actual cause of the concern (apparently serious employee error) was preventable, I was still impressed by their detailed disclosure, the steps that have been taken to mitigate it, and actual details about what was compromised other than the generic "non-credit card personal data".
I don't use MongoHQ for any projects right now (I evaluated their offering a year or so ago and opted to go with MongoLab, which I am still suing), but their response impressed me. There is indeed such a thing as screwing up properly, imho.
Kudos to the MongoHQ team, and best of luck in dealing with this mess.
- jdp23 13y ago> opted to go with MongoLab, which I am still suing this is either an unfortunate typo or a great backstory ...
- aroman 13y agoHah! Oh god, yep, that was a typo. Part of me wishes I had a cool backstory to tell though... (not that I think MongoLab is in the least deserves to be the object of such action, of course!)
- brandoncarl 13y agostill "suing"...hahaha. slightly different meaning the misspelling conveys, especially in this incident!
- seany 13y agoSeriously. I wish other services did security notifications with this much detail (I'm looking at you linode).
- camus2 13y agoI guess You meant "using" not "suing".
- clark-kent 13y agoI guess you are suing them for good service. Sorry HN for lack of insight, I really needed the laugh.