- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Mar 2022 23:17:09 +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*) I disagree. This is the result of this WG choosing to ignore accessibility and human interaction as part of our goal. Communication to users and how we chose our language is critical. As a result this standard is dense, overly technical, and confusing even for subject matter experts. How is the barrista at my cafe meant to understand "discoverable credential" or "resident key", or "direct vs none attestation". How can the users of the system we are creating be empowered, if they can't understand the soup of technical jibberish we keep throwing around? By ignoring the deployment use cases and the experience of both RP's in deployments and the experience of the humans that use these devices, we have created this situation. These marketing departments are not "idiotic" they are trying to create a human experience that is accessible to a diverse range of humans. I would encourage you to rethink your choice of words and attitude, and to empathise with peoples who backgrounds are different from your own. -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1708#issuecomment-1073370182 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 23:17:12 UTC