My main issue with these systems is that they tend to not be able to do anything beyond what I can do myself in whatever self-service portal is available. If I'm calling, it's because I need support beyond what the bot can probably provide, and it just becomes a matter of arguing with the robot to get to a human who can actually solve my problem.
Depends on how the dev wants to implement it, usually when I'm throwing a small animation on a site I'll silently respect the preference and skip the animation without an override option, but for a site like this I'd expect an override switch.
A more convenient manual that frequently spouts falsehoods, sure.
My favorite part is when it includes parameters in its output that are not and have never been a part of the API I'm trying to get it to build against.
Could also make it a site rule that _all_ jobs postings should include a pay range. Shouldn't have to waste your time applying to a job that has a pay range you would never accept.
I've found that face/retina scans are usually bad UX, especially if you need to use a viewfinder or a statically positioned device. Apple's Face ID works well because it's on a mobile device and you don't have to align your face in a box.
I don't see how this is any more convenient than using a mobile wallet. In fact, it looks less convenient than using the actual card - even if you forget the card you can usually just key in the number at the terminal.
I doubt this will change anything in the space. iOS and macOS (through Safari) has offered password management for years at this point. This is just a more flexible version of that system.
Washington doesn’t even officially offer a RealID. Instead they have the “Enhanced ID” which functions as a passport card but does not have the security features required on a RealID (though it does have some additional features like RFID).
I really hope the profile management system keeps tab containers working the same. It's incredibly useful to have different containers automatically generated for AWS console sessions.
> It's up to the server whether it uses it in challenge-response or not. That's application-specific behaviour that's past the definition of passkeys themselves.
Do you have a source for this? After reading the W3 spec[0] this seems entirely antithetical to the Passkey model and additionally raises concerns about the integrity of hardware mfa devices.
Surprised mobile boarding passes haven't changed to ticketmaster-style passes that leverage the phone's NFC capabilities. Seems like that would be faster to scan at the gate and prevent duplication.
This is the same behavior as SMS if you have enabled “Messages backup.” If backup is not enabled you will not have a copy of iMessages stored in iCloud (though all compatible and configured devices will still receive messages).
This can be changed by opting in to the e2ee iCloud data service “Advanced Data Protection.”
I’m curious how this works with the new ID-scanning machines that no longer require a boarding pass. Maybe there’s some level of fuzzy-matching name/sex/dob?
I assume for TSA Precheck users there’s some lookup that can just grab your KTN from the database from your ID and look up tickets based on that.