kgbme
EDIT Oh I see what you're saying; that's confusing, though, how's it supposed to work in the first place, then?? :))
A different kind of problem develops from there, because even though that biometric data is "secured" and encrypted (has to be, right?) - your signature still becomes available to "sync" and other system services...
We're, then, branded. No manufacturers and designers are taking steps to ensure that this kind of (deeply personal) data stays and functions strictly offline.
... As is the only way to keep your biometrics private (and truly secure). Keeping it isolated from network.
So, what's the best way: a password, a passcode, to keep in your head - or, a universal identifier which may be "unhackable", but universally known - to whoever. This can be a legit concern, no? :-s
EDIT: Right, sry, might've strayed off-topic there.
EDIT: Btw., what's the question as it is very broad? For example, for personal devices 2FA is a must... Somebody there has mentioned Kanye West using "0000", for his pwd.
ATM Skimmers is another huge issue, apparently, in certain countries: always have to carefully inspect the machine, prior to use.
Until recently, I had no idea that manufacturers actually PAY Google to have the services on Android... Talk about idiocy.
The way I see it, this - along with most of things - when you place the mechanisms there, people will use them and abuse them.
20 years ago, a browser had 3 MB and today they're 30 and 60 MB large, with much better compression of the installer.
Why do we need this-and-that service integration within the browser, to "follow trends" of the likes of Adobe, Microsoft?..
I don't think so. Cut it all out. Someone wants to watch a video: install a codec. Their service uses different coding? Tough luck, get with the (popular, useful) standard(s), or gtfo.
What the hell do I care about your corporate policy of "creating new jobs" and "advancing development", all you're doing -anyway- is peddling your products. In my browser. On my hardware, which I paid for, meh. Introducing 1000&1 vulnerabilities, where there should be none.
Right, wrong? Know what I mean?
It's awesome... Just saying. Despite of: https://jacquesmattheij.com/the-web-in-2050