- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Apr 2022 15:49:43 +0000
- To: public-patcg@w3.org
@csharrison another approach would be to structure the inclusion of matchkeys in the report as a key:value of provider:matchkey, instead of just a set of matchkeys, i.e.
```
{
"provider1.com": matchkey_1,
"provider2.com": matchkey_2,
...
}
```
Then, at query time, you could tell the aggregators: "only join on provider1.com". The aggregators could respect that choice in the joining, but still account for budgeting against the full set of matchkeys.
This still wouldn't fully solve the abuse scenario, however, because if someone were to simply set a uniform matchkey, that would likely still disrupt the budget accounting and contribution capping (in which case you'd still need reputational effects which @benjaminsavage proposes.)
--
GitHub Notification of comment by eriktaubeneck
Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/9#issuecomment-1112371919 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 15:49:44 UTC