Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To each their own, but I am far more interested in what happened, what they are doing about it, whether it can happen again, and why I heard aboutnit on HN instead of directly from Dropbox.

I personally am not interested in an apology or a gaveling tone. These people are not my personal friends, I don't have an emotional investment in whether they pretend to care about my feelings. I have an objective intrest in how they choose to act and the information they give me so that I can make my own informed choices.



I would really like to know the exact details of what happened.

Ideally I'd like to see the actual bug in code.


"I'd like to see the actual bug in code"

That makes it sound like it was primarily the fault of the developer who created the bug - things like this indicate an inadequate process or culture not simply a mistake at the developer level.

Edit: Does Dropbox have any testers or is all testing based on automated tests created by the development team?


Agreed. Sounds like the deployment wasn't QC'ed at all.


Not at all, why on earth do you think that?

I expect it wasn't obvious at all. I think that sharing the details with the community might help prevent others from making the same mistake.


And then what!? what will you do with your informed choices!

I think you are assuming too much.


Decide whether to keep using their services or to use a competitors?


Exactly.

Or decide how to balance the risk-benefit equation. Perhaps this will inform my choices of which things to keep in my dropbox and which to keep elsewhere. For example, I might decide that my secrets are fine there, but it is inappropriate to store client secrets in Dropbox since the client has certain expectations around my respect for their privacy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: