Perhaps they ought to disclose the IP address of the possible hack along with the method and specific technologies targeted in the breach. They should also provide the names and email addresses of the engineers helping fix the problem. They should have personally called every developer within the first 2 hours of the problem to inform them of exactly what line of code led to this utter mayhem.
I'm not sure how this affects their credibility at all. Does knowing within the first 10 seconds of the problem help you sell more apps or do your job any better? Did they make some kind of bullshit excuse? I think the emails I received were pretty clear. Remember that AWS failed two times in two weeks last year and they completely disabled AWS API access during those failures, which doesn't affect us downloading Xcode or dealing with provisioning, that affects live, production apps, that for many mean serious money. Remember how
Also, let's compare Amazon's response to a 2012 failure. The failure happened on a Friday night, taking completely out, a large number of web sites and applications, including Netflix, Pinterest and important to many developers, Heroku. Yet, it wasn't until Monday, that they released a statement explaining why, even when it was crystal clear it was power related. The kind of breach that Apple must have experience probably wasn't able to be forensically identified until many hours after the initial failure, yet in Amazon's case it was a power failure, which doesn't take a genius to need three days to release a statement.
I'm not defending Apple, but I am suggesting that our knee-jerk reactions be tempered by reality and how other companies have performed under similar situations.
