- From: Arnaud Dagnelies via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Feb 2022 14:11:22 +0000
- To: public-webauthn@w3.org
As a mere spectator and humble web developer, I can only shake my head when reading this. Of course every web developer would pull their hair when seeing something Uint8Array/ArrayBuffer/CBOR and by far favor base64 encoded data! It's so obvious, so clear. What's the point of having everyone write libraries around it, instead of making it usable directly? > On the call of 2020-01-22 it was decided that the use of ArrayBuffers is reflecting W3C direction as we understand it and that revisiting that would be too much. However, it does appear that implementations that don't care about attestation could be saved from worrying about CBOR if browsers were to parse out the public-key. The group believes that's worth pondering further and we're going to close this issue and open one focused on that. From an external and impartial point of view, this looks like shifting implementation effort from a few "providers" to countless "normal" web developers. Such an interface feels antiquated despite aiming to be the future of authentication. -- GitHub Notification of comment by dagnelies Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1362#issuecomment-1031509805 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 February 2022 14:11:24 UTC