I know. I didn't bring that up to accuse them of malice as far the DMCA part, I brought that up as an example that dropbox employees don't understand what their own internal tools do.
Re:New security issue at Dropbox
by SoftwareMaven on Monday June 20, 2011 @01:14PM
(#2675071)
I don't think that is as damning as you seem to. Once a company reaches more than a handful of people, knowing all the tools inside and out (especially in the divide between development and support, which this particular case highlighted) becomes impossible.
However, regardless of whether I feel like the previous event said anything about DropBox's development capabilities, I do feel like this event does.
I'm responsible for the authentication code for my company. I can't imagine having a default "YES" in any circumstance, and that DropBox did shakes my faith in them and their ability to protect my information significantly.
It came out in the aftermath that the takedown notice was the result of an automated process that was accidentally triggered.