Hi. Guy who does the autoscaling code here at Epic. It's really fun to watch the graphs of how many server sessions we have in a region at any given time over the course of a day.
I like that you're in here commenting. After reading through the postmortem, it reminds me of scaling issues we had at previous job. We had hundreds of thousands of clients that would get "hyper active" if they had issues connecting, retry loops FTW.
System goes down and it was hard resurrecting it since the traffic just kept pounding away. No autoscaling, no cloud. It woulda been handy to just fire up some more servers, let alone have things auto-scale via CPU %.
An incoming call isn't an alert. It's a highly time sensitive notification.
An alert is something that blocks further input until it is dismissed. Something along the lines of "Are you sure you want to disable encryption?" or "This item can not be deleted because it is locked."
I think that it was providing shortcuts for interacting with an alert already displayed on the main screen. Apple's worry, I'm assuming, is that alerts will be displayed only on the bar and people without the new Pro will not notice them.
You can't flash the firmware yourself, as the keys are discarded as soon as they're generated per device.
What you could do, however, is read the bits off of the firmware and make sure they're identical to the bits you make from source. Reproducible builds, and all that.
(I work at Epic on Team Online, aka the team that this whole PM is about.)