- From: Charlie Harrison via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2022 18:02:27 +0000
- To: public-patcg@w3.org
Quick initial thoughts reading this proposal: High level comment: I would prefer if we split out security and privacy constraints, mostly because I think we can have meaningful discussions about them in relative isolation without mixing things. I have strong concerns about enforcing k = 100 , since for some advertisers conversions can be quite rare events and even a relatively tight epsilon should give good data for many values of k < 100 (e.g. eps=1 will yield only a ~15% error on counts of 10). Regarding privacy unit / privacy grain, I think what is written now is stronger even than IPA which has a privacy unit of user x site. Did you intend to propose full user-level privacy here: "total amount of cross-site/cross-app information a caller can learn about a given person". We should try to be very precise about this. -- GitHub Notification of comment by csharrison Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/17#issuecomment-1163445235 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 June 2022 18:02:28 UTC