- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Mon, 23 Jun 2025 17:01:11 +0000
- To: public-fedid-wg@w3.org
- Message-Id: <E1uTkXf-00CNRW-3B@janus.w3.internal>
Issues
------
* w3c-fedid/FedCM (+6/-2/💬14)
6 issues created:
- Ask the [TAG](https://www.w3.org/2001/tag/) for review; see [how to work with the TAG](https://tag.w3.org/workmode/). If you are developing javascript APIs you may also want to ask public-script-coord@w3.org, a technical discussion list shared by W3C and ECMA's TC 39. (by wseltzer)
https://github.com/w3c-fedid/FedCM/issues/749
- Potential issue with Clear-Site-Data and unknown login status (by npm1)
https://github.com/w3c-fedid/FedCM/issues/746
- Add status checks to fetches (by npm1)
https://github.com/w3c-fedid/FedCM/issues/745
- `IdentityProvider.resolve()` idl doesn't show a returned `Promise` (by bvandersloot-mozilla)
https://github.com/w3c-fedid/FedCM/issues/742
- Accessibility review (by wseltzer)
https://github.com/w3c-fedid/FedCM/issues/741
- Work through [this questionnaire](https://w3c.github.io/apa/fast/checklist.html) then [request a review via GitHub](https://github.com/w3c/a11y-request/issues/new/choose) from [APA](https://www.w3.org/WAI/APA/) (by wseltzer)
https://github.com/w3c-fedid/FedCM/issues/740
7 issues received 14 new comments:
- #749 Architecture (TAG) review (2 by samuelgoto, wseltzer)
https://github.com/w3c-fedid/FedCM/issues/749
- #742 `IdentityProvider.resolve()` idl doesn't show a returned `Promise` in the IDL (1 by npm1)
https://github.com/w3c-fedid/FedCM/issues/742
- #741 Accessibility review (2 by kedruff, wseltzer)
https://github.com/w3c-fedid/FedCM/issues/741 [agenda+]
- #740 Accessibility (1 by wseltzer)
https://github.com/w3c-fedid/FedCM/issues/740
- #725 Support showing iframe origins in the UI, when they are third-party (1 by yi-gu)
https://github.com/w3c-fedid/FedCM/issues/725
- #700 Tracking through IDP with individualized account and client_metadata endpoints (6 by bvandersloot-mozilla, npm1, samuelgoto)
https://github.com/w3c-fedid/FedCM/issues/700
- #652 Horizontal Review preparation (1 by wseltzer)
https://github.com/w3c-fedid/FedCM/issues/652 [agenda+]
2 issues closed:
- `IdentityProvider.resolve()` idl doesn't show a returned `Promise` in the IDL https://github.com/w3c-fedid/FedCM/issues/742
- Accessibility https://github.com/w3c-fedid/FedCM/issues/740
* WICG/digital-credentials (+9/-6/💬29)
9 issues created:
- Exchanges user agency for greater compliance and convenience (by kdenhartog)
https://github.com/w3c-fedid/digital-credentials/issues/293
- Increased restriction of the ability to publish, view, and participate on the Web, and corresponding fragmentation of the Web as a whole (by kdenhartog)
https://github.com/w3c-fedid/digital-credentials/issues/292
- Prevent increased centralization of trust on the Web (by kdenhartog)
https://github.com/w3c-fedid/digital-credentials/issues/291
- define consent and permission; explain split roles regarding consent (by npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/290 [privacy-tracker]
- note designed-for-purpose alternatives and the risk of crowding out those options (by npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/289
- user agents should limit to protocols listed in the registry that meet the group's requirements (by npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/288 [privacy-tracker]
- Privacy Considerations for multiple presentation requests (and responses) (by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/286 [privacy-tracker] [privacy-considerations]
- Editorial: Add references to definitions in the privacy considerations (by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/284 [editorial]
- User agents that only support authorized verifiers (for government credentials) (by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/281 [privacy-tracker]
15 issues received 29 new comments:
- #289 note designed-for-purpose alternatives and the risk of crowding out those options (1 by RByers)
https://github.com/w3c-fedid/digital-credentials/issues/289 [privacy-tracker]
- #288 user agents should limit to protocols listed in the registry that meet the group's requirements (2 by npdoty, timcappalli)
https://github.com/w3c-fedid/digital-credentials/issues/288 [privacy-tracker]
- #281 User agents that only support authorized verifiers (for government credentials) (2 by RByers, johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/281 [privacy-tracker]
- #280 Can we require protocols to support unlinkable revocation? (5 by andrea-dintino, c2bo, johannhof, simoneonofri)
https://github.com/w3c-fedid/digital-credentials/issues/280 [privacy-tracker]
- #267 reporting abuse of credential requests (1 by npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/267 [privacy-tracker] [privacy-considerations]
- #247 Privacy Considerations: Ensuring user choice over wallet involvement (avoid wallet surveillance) (1 by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/247 [privacy-considerations]
- #244 Privacy Considerations: User permission and transparency (1 by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/244 [privacy-considerations]
- #241 Scope of Privacy Considerations (1 by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/241 [privacy-considerations]
- #226 privacy review for registry inclusion (2 by npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/226 [privacy-tracker] [privacy-considerations]
- #201 multi-wallet requests (1 by npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/201
- #133 Consider requiring mitigation of script injection attacks. (2 by johannhof, npdoty)
https://github.com/w3c-fedid/digital-credentials/issues/133 [future] [security-tracker] [security-considerations]
- #108 Explainer: no mention of what security and privacy properties of a request are desireable (1 by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/108 [explainer]
- #105 Privacy: ensuring RPs blinded to credential existence (1 by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/105 [spec]
- #35 [Discuss] This API should address the Jevons Paradox around increased consumption of verifiable credentials and the rise of their abuses (7 by DemiMarie, c2bo, johannhof, kdenhartog, timcappalli)
https://github.com/w3c-fedid/digital-credentials/issues/35 [discussion] [privacy-tracker]
- #30 [Discuss] Abuse preventions and mitigations (1 by johannhof)
https://github.com/w3c-fedid/digital-credentials/issues/30 [discussion]
6 issues closed:
- protocol identifier is undefined https://github.com/w3c-fedid/digital-credentials/issues/270
- Privacy Considerations: Ensuring user choice over wallet involvement (avoid wallet surveillance) https://github.com/w3c-fedid/digital-credentials/issues/247 [privacy-considerations]
- Privacy Considerations: User permission and transparency https://github.com/w3c-fedid/digital-credentials/issues/244 [privacy-considerations]
- Scope of Privacy Considerations https://github.com/w3c-fedid/digital-credentials/issues/241 [privacy-considerations]
- Explainer: no mention of what security and privacy properties of a request are desireable https://github.com/w3c-fedid/digital-credentials/issues/108 [explainer]
- [Discuss] Abuse preventions and mitigations https://github.com/w3c-fedid/digital-credentials/issues/30 [discussion]
Pull requests
-------------
* w3c-fedid/FedCM (+4/-7/💬6)
4 pull requests submitted:
- s/triples/quadruples (by npm1)
https://github.com/w3c-fedid/FedCM/pull/748
- Fix typo with resolve (by npm1)
https://github.com/w3c-fedid/FedCM/pull/744
- Make resolve return a Promise (by npm1)
https://github.com/w3c-fedid/FedCM/pull/743
- Corrected the link at Step 4 (by pottis)
https://github.com/w3c-fedid/FedCM/pull/739
4 pull requests received 6 new comments:
- #748 s/triples/quadruples (1 by cbiesinger)
https://github.com/w3c-fedid/FedCM/pull/748
- #743 Make resolve return a Promise (2 by npm1)
https://github.com/w3c-fedid/FedCM/pull/743
- #678 Specify "Use another account". (1 by cbiesinger)
https://github.com/w3c-fedid/FedCM/pull/678 [agenda+]
- #498 Add API to show error messages from failed token fetches (2 by npm1, yi-gu)
https://github.com/w3c-fedid/FedCM/pull/498 [agenda+] [chrome]
7 pull requests merged:
- s/triples/quadruples
https://github.com/w3c-fedid/FedCM/pull/748
- Specify "Use another account".
https://github.com/w3c-fedid/FedCM/pull/678 [agenda+]
- Make connected accounts set a quadruple
https://github.com/w3c-fedid/FedCM/pull/732 [agenda+]
- Fix typo with resolve
https://github.com/w3c-fedid/FedCM/pull/744
- Make resolve return a Promise
https://github.com/w3c-fedid/FedCM/pull/743
- Corrected the link at Step 4
https://github.com/w3c-fedid/FedCM/pull/739
- Inspecting FedCM API network requests within DevTools
https://github.com/w3c-fedid/FedCM/pull/738
* WICG/digital-credentials (+4/-5/💬15)
4 pull requests submitted:
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c-fedid/digital-credentials/pull/294
- Add additional issues to privacy considerations (by johannhof)
https://github.com/w3c-fedid/digital-credentials/pull/287
- Clean up privacy considerations TODO sections (by johannhof)
https://github.com/w3c-fedid/digital-credentials/pull/285
- Add initial privacy considerations for fingerprinting and data leakage (by johannhof)
https://github.com/w3c-fedid/digital-credentials/pull/283
8 pull requests received 15 new comments:
- #283 Add initial privacy considerations for fingerprinting and data leakage (5 by johannhof, npdoty)
https://github.com/w3c-fedid/digital-credentials/pull/283 [privacy-considerations]
- #278 Add design considerations section to privacy considerations (fixes #275) (2 by johannhof, npdoty)
https://github.com/w3c-fedid/digital-credentials/pull/278
- #277 Security Considerations: Writing first round of threats and mitigatio… (1 by marcoscaceres)
https://github.com/w3c-fedid/digital-credentials/pull/277 [security-tracker] [security-considerations]
- #276 Formally define 'protocol identifier' (1 by marcoscaceres)
https://github.com/w3c-fedid/digital-credentials/pull/276
- #262 Write initial privacy considerations for unnecessary use (1 by burdges)
https://github.com/w3c-fedid/digital-credentials/pull/262 [privacy-considerations]
- #260 Add initial privacy considerations section for protocol requirements (3 by johannhof, mohamedamir)
https://github.com/w3c-fedid/digital-credentials/pull/260 [privacy-considerations]
- #253 Add initial text for permission & transparency (1 by npdoty)
https://github.com/w3c-fedid/digital-credentials/pull/253 [privacy-considerations]
- #179 Require JSON serialization checks coming in (1 by marcoscaceres)
https://github.com/w3c-fedid/digital-credentials/pull/179 [BLOCKED]
5 pull requests merged:
- Tidied up document using tidy-html5
https://github.com/w3c-fedid/digital-credentials/pull/294
- Formally define 'protocol identifier'
https://github.com/w3c-fedid/digital-credentials/pull/276
- Clean up privacy considerations TODO sections
https://github.com/w3c-fedid/digital-credentials/pull/285 [privacy-considerations]
- Add additional issues to privacy considerations
https://github.com/w3c-fedid/digital-credentials/pull/287 [privacy-considerations]
- Tidied up document using tidy-html5
https://github.com/w3c-fedid/digital-credentials/pull/282
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c-fedid/FedCM
* https://github.com/w3c-fedid/proposals
* https://github.com/w3c-fedid/login-status
* https://github.com/w3c-fedid/idp-registration
* https://github.com/w3c-fedid/multi-idp
* https://github.com/w3c-fedid/custom-requests
* https://github.com/w3c-fedid/active-mode
* https://github.com/w3c-fedid/delegation
* https://github.com/fedidcg/LightweightFedCM
* https://github.com/fedidcg/proposals
* https://github.com/WICG/digital-credentials
* https://github.com/privacycg/is-logged-in
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 June 2025 17:01:13 UTC