[meetings] Agenda Request - Keeping good ads off bad sites (#49)
Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
- Re: [private-measurement] Interoperable Private Attribution (IPA) (#9)
[meetings] May 2022 Meeting (#48)
Closed: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
Closed: [meetings] Agenda Request - Call for Consensus on Charter Issue: "chair selection is complex and open to abuse" (#41)
Re: [meetings] Agenda Request - Call for Consensus on Charter Issue: "chair selection is complex and open to abuse" (#41)
Closed: [meetings] Update on Privacy Principles (#43)
[patcg.github.io] Pull Request: Fix CG name in body copy
Closed: [proposals] Interest Based Advertising with the Topics API (#4)
[patwg-charter] Pull Request: Update charter.html
- Re: [patwg-charter] Update charter.html (#20)
- Re: [patwg-charter] Update charter.html (#20)
- Re: [patwg-charter] Update charter.html (#20)
- Re: [patwg-charter] Update charter.html (#20)
- Re: [patwg-charter] Update charter.html to better define privacy (#20)
- Re: [patwg-charter] Update charter.html to better define privacy (#20)
- Re: [patwg-charter] Update charter.html to better define privacy (#20)
Re: [proposals] Collection of known research and literature on user perceptions of (novel) privacy enhancing technologies (#10)
[proposals] How do I enter my proposal into the individual drafts space? (#12)
Closed: [admin] Meeting: 5th & 7th April 2022 (#4)
Re: [meetings] Privacy Principles for Web Advertising Features - Editorial Group (#18)
Closed: [meetings] Agenda Request - Consider the Reach and Frequency Use Case for Ads Measurement (#12)
Closed: [meetings] Taking up Topics API for Next Meeting or Future Meeting? (#32)
Re: [meetings] Taking up Topics API for Next Meeting or Future Meeting? (#32)
Closed: [meetings] April 2022 Meeting (#34)
Closed: [meetings] Refine and finalize Agenda (#37)
Re: [proposals] Interest Based Advertising with the Topics API (#4)
Closed: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)
[patwg-charter] Pull Request: Fix markup typo
[patcg.github.io] Closed Pull Request: Adding a clear incubation process and flow
[patwg-charter] Pull Request: Following discussion with a number of colleagues this PR covers issue…
Closed: [patcg.github.io] chair selection is complex and open to abuse (#1)
[patcg.github.io] Merged Pull Request: chairs don't immediately vacate upon election
[patcg.github.io] Merged Pull Request: Define a way for the CG to perform community-focused tasks on behalf of the WG
Closed: [patcg.github.io] clarify deliverables of the group (#4)
[patcg.github.io] Merged Pull Request: More text for deliverables
[patcg.github.io] Closed Pull Request: briefer chair selection: by consensus
Re: [patcg.github.io] chairs don't immediately vacate upon election (#9)
Re: [patcg.github.io] briefer chair selection: by consensus (#10)
[private-measurement] Feature Discussion: Managing Collusion Risk (#13)
[private-measurement] Questions about Collusion - What can be done about the collusion risk in these systems? (#12)
[patcg.github.io] Pull Request: Individual area
- Re: [patcg.github.io] Individual area (#15)
- Re: [patcg.github.io] Individual area (#15)
- [patcg.github.io] Merged Pull Request: Individual area
[private-measurement] Discuss the Machine Learning Use Case (#11)
Re: [private-measurement] Feature Discussion: High Risk Contexts (#6)
- Re: [private-measurement] Feature Discussion: High Risk Contexts (#6)
- Re: [private-measurement] Feature Discussion: High Risk Contexts (#6)
- Re: [private-measurement] Feature Discussion: High Risk Contexts (#6)
- Re: [private-measurement] Feature Discussion: High Risk Contexts (#6)
- Re: [private-measurement] Feature Discussion: High Risk Contexts (#6)
[private-measurement] Considering distributing trust in the context of these proposals (#10)
Re: [private-measurement] Generate Test Cases for Evaluations (#7)
- Re: [private-measurement] Generate Test Cases for Evaluations (#7)
- Re: [private-measurement] Generate Test Cases for Evaluations (#7)
- Re: [private-measurement] Generate Test Cases for Evaluations (#7)
- Re: [private-measurement] Generate Test Cases for Evaluations (#7)
Re: [patcg.github.io] Charter needs to allow for competitive solutions not exclusively controlled by browsers (#5)
Re: [patwg-charter] jwrosewell: "across multiple devices and browsers" (#7)
- Re: [patwg-charter] jwrosewell: "across multiple devices and browsers" (#7)
- Re: [patwg-charter] jwrosewell: "across multiple devices and browsers" (#7)
Re: [patwg-charter] Community stakeholder feedback collection process (#14)
Re: [patwg-charter] Adding link to Decisions section of Process document (#15)
[patwg-charter] Merged Pull Request: Adding link to Decisions section of Process document
Closed: [patwg-charter] What does due process mean (#11)
[meetings] Pull Request: Update README.md
[patwg-charter] Pull Request: Consistency on Success/Deliverables
- Re: [patwg-charter] Consistency on Success/Deliverables (#17)
- Re: [patwg-charter] Consistency on Success/Deliverables (#17)
Re: [patwg-charter] What does due process mean (#11)
Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
- Re: [patcg.github.io] Adding a clear incubation process and flow (#7)
Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
- Re: [patwg-charter] Ben Savage: Need to define Privacy (#6)
[patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
- Re: [patwg-charter] Charter scope and guaranteeing availability of input data (#16)
Re: [patwg-charter] jwrosewell: Do not reference S&P questionnaire (#10)
- Re: [patwg-charter] jwrosewell: Do not reference S&P questionnaire (#10)
- Re: [patwg-charter] jwrosewell: Do not reference S&P questionnaire (#10)
- Re: [patwg-charter] jwrosewell: Do not reference S&P questionnaire (#10)
- Re: [patwg-charter] jwrosewell: Do not reference S&P questionnaire (#10)
[patcg.github.io] Pull Request: add link to join
[patcg.github.io] Add link to join (#13)
Closed: [meetings] Meeting Cadence and Timing? (#4)
[meetings] Call for Scribes - 2022-04 Meeting (#46)
- Re: [meetings] Call for Scribes - 2022-04 Meeting (#46)
- Re: [meetings] Call for Scribes - 2022-04 Meeting (#46)
- Re: [meetings] Call for Scribes - 2022-04 Meeting (#46)
- Re: [meetings] Call for Scribes - 2022-04 Meeting (#46)
- Re: [meetings] Call for Scribes - 2022-04 Meeting (#46)
- Re: [meetings] Call for Scribes - 2022-04 Meeting (#46)
- Closed: [meetings] Call for Scribes - 2022-04 Meeting (#46)
Re: [patwg-charter] Where do we propose to advance to, CR or PR? (#9)
- Re: [patwg-charter] Where do we propose to advance to, CR or PR? (#9)
- Re: [patwg-charter] Where do we propose to advance to, CR or PR? (#9)
- Re: [patwg-charter] Where do we propose to advance to, CR or PR? (#9)
Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
- Re: [meetings] Agenda Request - Should PATCG be opinionated on which technologies are used to enable privacy? (#39)
Re: [patcg.github.io] Define a way for the CG to perform community-focused tasks on behalf of the WG (#12)
Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
- Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)
Re: [meetings] April 2022 Meeting (#34)
[meetings] Pull Request: Initial Draft of Agenda
- Re: [meetings] Initial Draft of Agenda (#45)
- [meetings] Merged Pull Request: Initial Draft of Agenda
Re: [meetings] Chartering the Working Group (#7)
Re: [meetings] Agenda Request - Collective Governance of Infrastructure (#40)
Re: [meetings] Agenda Request - Consider the Reach and Frequency Use Case for Ads Measurement (#12)
- Re: [meetings] Agenda Request - Consider the Reach and Frequency Use Case for Ads Measurement (#12)
- Re: [meetings] Agenda Request - Consider the Reach and Frequency Use Case for Ads Measurement (#12)
[meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Re: [meetings] Agenda Request - Operational experience with MPC (#44)
- Closed: [meetings] Agenda Request - Operational experience with MPC (#44)
Re: [meetings] Update on Privacy Principles (#43)
Re: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)
- Re: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)
- Re: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)
- Re: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)
- Re: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)
- Re: [meetings] Agenda Request - Call for Progress Report on Private Measurement (#42)