Accompanying @akshayku's [outline of Windows' thinking](https://github.com/w3c/webauthn/issues/1691#issuecomment-1021442625) (above), chrome's position on RP's discriminating amongst authenticators, passkey emergence, etc, is [summarized in this post](https://github.com/w3c/webauthn/issues/1688#issuecomment-1011516074) by @agl on issue #1688 As noted in [Explainer: broadening the user base of WebAuthn](https://github.com/w3c/webauthn/wiki/Explainer:-broadening-the-user-base-of-WebAuthn), the overall goal with passkeys and the accompanying various features, the overall goal is "...to make WebAuthn more broadly applicable as a password replacement." -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1691#issuecomment-1022535768 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Wednesday, 26 January 2022 19:36:24 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:45 UTC