- From: Charlie Harrison via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Apr 2022 01:53:21 +0000
- To: public-patcg@w3.org
Yes (1) makes sense and I think it's specified in the doc. (2) doesn't fully cover the second comment though. I could ask all my partner sites to pre-commit to use fb1.com / fb2.com as identity providers without doing any kind of rotation / switching. Then I just double up all my source / trigger events (one per each match key provider) and get effectively double counts for the same privacy budget. I think what you might have to do (and maybe this is what you were implying with (2)) is that if you pre-commit to N match key providers, you would effectively have more noise added to your aggregations scaled with N to keep similar privacy guarantees and get closer to the user+site grain. -- GitHub Notification of comment by csharrison Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/9#issuecomment-1111653910 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 April 2022 01:53:22 UTC