- Last Active
Twitter login error:
Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings.
Anyhow, hentaiboy said:Apple watch data will show he got cold feet and did a runner from his bride to be 😂
Considering they believe he was literally sawed into pieces with a bone saw, this is an extremely insensitive comment.
pmc said:Great site and thank you for the articles HOWEVER, that is not what begging the question means.
Wikipedia has this as an example of, “begging the question”:Left-handed people are better painters because right-handed people can't paint as well.
The argument (left-handed people are better painters) is supported by the second part (right-handed people can’t paint as well [as left-handed people]), which is erroneous and also asserts the same basic premise as the first.
This is the GM of iOS 12 because the next release won’t be.
... would be begging the question.
ihatescreennames said:Well, sure, if a screen shot is all that’s required, but I doubt that’s the way it would work. Just like when I use Apple Pay it’s not just an image of a credit card that enables my payment.
My app + web service allow an end-user to scan the barcode of a physical ID and take a "selfie" (as much as I hate that word). The online service then uses AWS Rekognition to compare the face in an on-file photo (e.g., your RMV photo) against the "selfie" (it knows which photo to use as a comparison from an identifier in the barcode data). If there's a match, it returns a Digital ID you can "Add to Apple Wallet".
I agree 100% with you that the verifiable, machine-readable data should not be shown until after the ID is "unlocked" via biometrics (or PIN) ... much like Apple Pay.
As for NFC (I received Apple's permission to use NFC-enabled passes for my testing), it's actually very complicated. The biggest challenge is that Apple Wallet NFC data exchange requires bi-directional communication between the Apple Wallet "pass" and the reading terminal ... and the terminal needs to request data using a specific identifier. This wouldn't be an issue if one Digital ID company had a monopoly in the US (therefore allowing all readers to be programmed to ask for that one company's specific identifier), but that's extremely unlikely to happen ... but then how are readers setup to "request" from possibly 50 different identifiers?
My conclusion is that, while sexy, NFC for driver's licenses (in America, anyways) is probably a bridge too far. I think a QR code w/ a cryptographic digital signature (+ some other modifications to Apple Wallet) is the way to go.
tallest skil said:boxcatcher said:
- Bar / clubs / casinos
- Picking up tickets at a will-call window
- Checking in to a hotel room
- Grocery store (buying alcohol or cigarettes)
- Renting a car
- TSA checkpoints