It's a really cool discovery, but I don't know how Apple is suppose to program against it.
What surprises me is how much of a time range each photo has to work with. Enough time for Tessa to put down one arm and then the other. It's basically recording a mini-video and selecting frames from it. I wonder if turning off things like Live Photo (which retroactively starts the video a second or two before you actually press record) would force the Camera app to select from a briefer range of time.
Maybe combining facial recognition with post processing to tell the software that if it thinks it's looking at multiple copies of the same person, it needs to time-sync the sections of frames chosen for the final photo. It wouldn't be foolproof, but it would be better than nothing.
The article is very unclear. It keeps waffling between "it'll keep working." and "it might stop working."
I'm just wondering if it stops working because of an unforeseen problem or because Steam says "I cannot update, so I won't run."
It's not Steam's fault, but I have to hang on to this old battleship for a few more years before I can replace it with hardware current enough to run current software.
Those of us that already have Steam games installed on Mojave will no longer be able to update? Or will Gaben reach into my computer and forbid me access to content I paid for?
Edit: All this anger for asking a relevant question. I learned my lesson.
Yeah, it's commonly thought to have something to do with security. Similar to chain of custody for criminal evidence.
Engineering compiles a department report for the captain. The Shift Lead puts the data on a PADD, then gives that PADD to the Chief Engineer. The Chief Engineer signs the data with their command code and notes that it is PADD-1217. That data then becomes locked to that PADD. Someone from Engineering is assigned to take PADD-1217 to the bridge and hand deliver it to the Captain. The Captain receives the PADD, reviews the report, confirms that they are holding PADD-1217, and signs the report with their command code. Someone from Engineering is sent to retrieve the PADD, and re-deliver it to the Chief Engineer. The Chief Engineer confirms the PADD was read and signed by the Captain, confirms it is PADD-1217, and transfers the signed data to the computer core to be logged and archived. The Chief Engineer then confirms all data on the PADD has been transferred and erased, then stores the PADD until it is needed again.
This is why it's common to see a pile of PADDs on the Captain's desk. Each department is sending their own secure report on their own PADD.
"Misuse"
You can take my Q-tips from deep within my cold, dead ear canals.