Sam Goto

> I'd be ok with just "requests" tho, but presentationRequests is also pretty clear. I'd prefer something short as `requests` rather than `presentationRequests`, since it it is going to go...

> Ok, requests it is... will send a PR soon. Something that we should ponder on is our tolerance to backwards incompatible changes (like this one) and where to draw...

> Mindful also that .identity. will also go away soon hopefully once we fix w3c/webappsec-credential-management#244 I didn't get the sense that Mozilla was supportive of that change.

> I’m still feeling pretty strongly we should have the single entry point, but could be convinced otherwise. I expanded a bit where I stand in that thread: https://github.com/w3c/webappsec-credential-management/issues/244#issuecomment-2297078104

> Directed identifiers don't really make a lot of sense in the vaunted "three party model" where the credential is typically issued with no conception of where it will be...

I'm a big proponent of https://github.com/WICG/PEPC and have been exploring ways in which we can use it with FedCM, so I share @mikewest 's intuition that it can raise the...

> would that still result in user interaction "you don't have a wallet that can fulfill this request?". Yeah, I think that's what Android is converging to: show a "no...

I'm concerned about this here: https://github.com/WICG/digital-credentials/pull/164

@marcoscaceres and I chatted briefly about this today and so far we think this could work between Chrome and Safari if we introduced the notion of a pre-defined value of...

> That seems... messy to be honest. What were the concerns with the method taking an input parameter with a protocol name? Ah, I remembered why @marcoscaceres and I arrived...