Matthew Miller

I've got a PR up over in the docs site repo to add the guidance I mentioned above: https://github.com/MasterKale/SimpleWebAuthn-homepage/pull/79

I'll make a PR with the "verify" to "assert" swap and see if this issue can simply be addressed in this way.

Is it only one-at-a-time for "user privacy" reasons? I see in https://github.com/w3c-fedid/digital-credentials/issues/168#issuecomment-2397446042 that "boolean testing is often preferred to providing a set for privacy reasons," but hypothetical use of the...

Thinking about this method's API, what about something like this instead? ```ts const supported = await DigitalCredential.getClientSupportedProtocols(); if (supported.includes('openid4vp')) { // Call DC API w/OID4VP } else if (supported.includes('fooproto')) {...

Hello @Mykhailo-Sichkaruk, thanks for the suggestion! This is a great idea, I see how it'd be nice to bring some order to the many more errors that @simplewebauthn/server might raise....

@dependabot rebase

I worked my way through the [FAST Checklist](https://w3c.github.io/apa/fast/checklist.html) but ended up with the following two potential items to address: 1. **Accessibility features can be internationalized to the same degree as...

From WG Meeting @ 4/30: There are opportunities to normatively define that multiple items in the `requests` array are "either/or", only one will be responded to. We should also try...

@dependabot rebase

> Sites checking whether cross-device is available and only requesting credentials from cross-device-supporting browsers would seem to punish developers of wallet software that runs on common devices. From a verifier...