- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 24 Feb 2025 17:01:14 +0000
- To: public-fedid-wg@w3.org
- Message-Id: <E1tmbpS-003SRE-2i@janus.w3.internal>
Issues
------
* w3c-fedid/FedCM (+2/-0/💬7)
2 issues created:
- Why is the client_metadata_endpoint required in the config response? (by togamid)
https://github.com/w3c-fedid/FedCM/issues/701
- Tracking through IDP with individualized account and client_metadata endpoints (by togamid)
https://github.com/w3c-fedid/FedCM/issues/700
3 issues received 7 new comments:
- #701 Why is the client_metadata_endpoint required in the config response? (1 by npm1)
https://github.com/w3c-fedid/FedCM/issues/701
- #700 Tracking through IDP with individualized account and client_metadata endpoints (3 by npm1, togamid, wparad)
https://github.com/w3c-fedid/FedCM/issues/700
- #652 Horizontal Review preparation (3 by npm1, simoneonofri)
https://github.com/w3c-fedid/FedCM/issues/652 [agenda+]
* w3c-fedid/delegation (+0/-0/💬3)
1 issues received 3 new comments:
- #3 Pseudonymous Credentials (3 by SamuelSchlesinger, joshcornejo)
https://github.com/w3c-fedid/delegation/issues/3 [agenda+]
* WICG/digital-credentials (+0/-2/💬12)
7 issues received 12 new comments:
- #203 Just a little help with credential verification (2 by mmachado53, timcappalli)
https://github.com/WICG/digital-credentials/issues/203
- #201 multi-wallet requests (1 by timcappalli)
https://github.com/WICG/digital-credentials/issues/201
- #191 What are the protocol identifier naming rules? (1 by marcoscaceres)
https://github.com/WICG/digital-credentials/issues/191 [spec] [registry]
- #167 How should we go about issuance? (1 by marcoscaceres)
https://github.com/WICG/digital-credentials/issues/167 [issuance]
- #160 Handling various origin types (1 by timcappalli)
https://github.com/WICG/digital-credentials/issues/160 [spec]
- #102 Managing request format extensibility without sacrificing security (1 by marcoscaceres)
https://github.com/WICG/digital-credentials/issues/102 [discussion] [pending closure]
- #44 API requests should provide the site with what they need to explain why and how requested credential information will be used (5 by jogu, npdoty, timcappalli)
https://github.com/WICG/digital-credentials/issues/44 [enhancement] [dc2-proposal]
2 issues closed:
- Managing request format extensibility without sacrificing security https://github.com/WICG/digital-credentials/issues/102 [discussion] [pending closure]
- Just a little help with credential verification https://github.com/WICG/digital-credentials/issues/203
Pull requests
-------------
* w3c-fedid/FedCM (+0/-0/💬1)
1 pull requests received 1 new comments:
- #686 Add single-get multi IDP support for passive mode (1 by npm1)
https://github.com/w3c-fedid/FedCM/pull/686
* WICG/digital-credentials (+1/-0/💬0)
1 pull requests submitted:
- Issuance attempt (by mohamedamir)
https://github.com/WICG/digital-credentials/pull/204
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, 24 February 2025 17:01:15 UTC