Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda Request - Private measurement of single events #112

Closed
csharrison opened this issue Apr 10, 2023 · 5 comments
Closed

Agenda Request - Private measurement of single events #112

csharrison opened this issue Apr 10, 2023 · 5 comments
Assignees

Comments

@csharrison
Copy link
Collaborator

Agenda+: Private measurement of single events

I wanted to discuss patcg/docs-and-reports#41 with the group. Here I outline a potential implication of using differential privacy as our primary privacy definition, and I want to gauge the group's comfort with this. Given that we are already roughly aligned on at least DP for our privacy definition, the outcome of this discussion would be to either:

  • Further entrench that differential privacy matches what we want
  • Augment our privacy definition to include some auxiliary privacy notion to protect us more against measuring single events

Time

30-60 minutes

Links

@csharrison csharrison added the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Apr 10, 2023
@AramZS
Copy link
Contributor

AramZS commented Apr 11, 2023

Adding to the Agenda!

@benjaminsavage
Copy link

I'm looking forward to discussing this. I think it's an important discussion to have.

In the context of this discussion, I'd like to discuss the various approaches one could attempt to deploy if we were to decide that we did not want to enable the "private measurement of single events".

For example, we could have an initial pass over the inputs, to ensure that there were at least K input events from a given breakdown key.

Such a system would still not completely prevent websites from attempting to measure single events, since they could just generate K-1 fake events and combine it with one real event.

But such a system could potentially make it economically unattractive to do so, by effectively multiplying the cost of such measurement by a factor of K.

@benjaminsavage
Copy link

I would really like to hear @johnwilander weigh in on this topic (Private Measurement of Single Events).

John, do you think you'll be able to make it to the next PAT-CG to talk about this? I think it's really important to make sure Webkit's stance on this is on the record.

@csharrison
Copy link
Collaborator Author

Here is the deck I plan on presenting tomorrow.

@AramZS AramZS added the call-for-consensus Indicates a PR or Issue is at a state where we are calling for participents to reach consensus label May 16, 2023
@AramZS
Copy link
Contributor

AramZS commented May 16, 2023

Hi all, it appears we have come to an agreement on merging in the discussed changes in the meeting. I think it is reasonable to close on Thursday (2 weeks following the proposal). I wanted to note in this repo in case folks had missed it that this was text change was near resolution - patcg/docs-and-reports#43

@AramZS AramZS removed agenda+ Request to add this issue to the agenda of our next telcon or F2F call-for-consensus Indicates a PR or Issue is at a state where we are calling for participents to reach consensus labels May 18, 2023
@AramZS AramZS closed this as completed May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants