- From: Arshad Noor via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Mar 2022 10:36:31 +0000
- To: public-webauthn@w3.org
This is the sorry result of companies choosing to ignore educating businesses and consumers about "FIDO". As a consequence, we've ended up with: * FIDO * WebAuthn * Windows Hello * Passkey * ... IMO, companies who wish to save themselves time/money avoiding having to repeatedly explain the idiocy of marketing departments (who do not understand the reason for standardized names for complex technical concepts*) should stick to one of the following messages: * "Register your FIDO credential" * "Register your passwordless credential" or * "Register your credential" I would also encourage having a link on the site to educate consumers - at a high level - about what is going on; this site from the FIDO Alliance is helpful: https://loginwithfido.com. Arshad Noor StrongKey /* Imagine what the state of the internet might be today if companies had chosen to brand TCP/IP with names their marketing departments chose instead of what the RFC defined - a few of us might still have been programming with COBOL while the rest of us would have been pushing paper forms to feed that machine. / On 3/19/22 10:45 AM, certainlyNotHeisenberg wrote: > > (This is not an issue but a question for the community. Just not sure > where else to ask it. Apologies if this is the wrong place!) > > I'm using WebAuthn and unsure what language to use so the user > understands what's happening. I'd love anyone's input! > > Specifically, I'm using the user's email address as the display name > and defaulting to platform authenticators. So, there are two steps, > where step 1 is "Enter Your Email". But I'm unsure what to call step 2. > > I started with "Complete Biometric", but the platform authenticator > won't always be a biometric — sometimes it'll be a passcode, or > pattern, or PIN, etc. > > Then I tried the slightly more generic "Complete Biometric/Passcode > Check", but that's a mouthful and still not totally accurate. > > Then I tried to see if I could customize the language based on the > platform (e.g. "Complete Face ID" on a certain iPhone, "Complete Touch > ID" on a different iPhone, etc.), but there are issues with that: > > * There's no totally reliable way to know what platform the user is on. > * Even if you know the platform, there are often several options at > the device level for what the platform authenticator would be. > (E.g. on an RCA Q2 phone I have, I can set in phone settings the > authenticator to be a passcode, PIN, or pattern.) > > Another issue with the generic "biometric" term is that it can sound > somewhat scary. The term itself doesn't distinguish between a platform > biometric like Face ID, which users find familiar, and a whole new > biometric like a third party facial recognition system, which users > often find quite invasive. > > I suppose "Complete Platform Authenticator Check" is the most > accurate... but I doubt many users would have any clue what that means. > > So I'm at a loss for what language to use! Any ideas would be very > welcome. :) > > — > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webauthn/issues/1708>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABWSVTWGDYUVQFGYT4IPQ5TVAYHFFANCNFSM5REJTAQA>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you are subscribed to this > thread.Message ID: ***@***.***> > -- GitHub Notification of comment by arshadnoor Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1708#issuecomment-1073220876 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 March 2022 10:36:32 UTC