Quote:
Originally Posted by etill
The other thing I thought was pretty decent is that he's owned the mistake, and been transparent about it from the start. Not every one will do that, it's easy to make something up and blame a provider
|
This was the bit that impressed me most. Amazon S3 didn't fail in the slightest. He deleted the files by a script, and versioning (offered by S3 in 2015 but not enabled/paid for) was not enabled. He documented this and apologised.
He may have had a slip of competence, but he's straight as an arrow by my standards.