- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 May 2022 22:22:07 +0000
- To: public-patcg@w3.org
> It's worth thinking through this scenario to see if we could detect / tolerate this. As far as I understand things, it is notoriously difficult for 1Ps to make configuration changes on their sites, so if we are relying on that to deter cheaters it's not ideal. I agree if we're talking about a cheater using information from site A to impact something about site B. However, if site A is willing to give a "cheater" ability to execute JS on their site, how we can prevent anything beyond that. > For a given report in the MPC system, how do we know the site it is associated with for purposes of budget? This is a good question. I have a few ideas here, but there are some tradeoffs. I'll open an issue for this specifically once the other repo is created. -- GitHub Notification of comment by eriktaubeneck Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/9#issuecomment-1120051378 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 May 2022 22:22:08 UTC