Who wrote this update? > As we said previously, the incident was a result of a server configuration change that allowed improper access by an unauthorized thir

Who wrote this update? > As we said previously, the incident was a result of a server configuration change that allowed improper access by an unauthorized third party. It opens needlessly defensive / combative, and then is sparse everywhere else. A week later you've confirmed passwords and credit card information wasn't at risk?! A server configuration allowed access to your source code and some data warehouse?! > We’ve undergone a thorough review of the information included in the files exposed and are confident that it only affected a small fraction of users and the customer impact is minimal. The small fraction of users is your most prominent, who drive the majority of your advertising revenue. The impact is minimal?! Every viewer now knows how much creators make (I understand they could infer previously, now they visit a <website> and know it with full confidence). You don't think it'll impact their desire to donate, as a most obvious example? Show Emmett Shear the door (finally), give this to AWS and let those folks manage it please.