- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 May 2022 16:38:15 +0000
- To: public-patcg@w3.org
`campaign_id` is probably a bad name, TBH. `group_id` is better, and because the `source_event` is sent back in the context it was called, it shouldn't need to be bound to the event when called. I've been thinking that one could assign the `group_id` after the fact (and even change it for two different queries.) The only restriction would be reaching the set grouping threshold (+DP noise). I haven't thought about assigning multiple `group_id`s to a single event within a single query, and I have the same intuition around increasing complexity in the MPC. Are there scenarios where this would be important to have multiple in a single query (as opposed to sequential, independent queries?) -- GitHub Notification of comment by eriktaubeneck Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/9#issuecomment-1121329028 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 May 2022 16:38:16 UTC