- From: Charlie Harrison via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 May 2022 14:07:58 +0000
- To: public-patcg@w3.org
Can you elaborate why an HTTPS response does not adequately address the provenance issue? Are you discussing here a use-case where actor A is trying to generate reports based on events caused by actor B? I think if the platform is the one which needs to know provenance, having a secure connection to the actor creating the event seems sufficient. On 2, this makes sense to me, that was my understanding of the system from reading the doc. It seems like we will need substantial coordination and centralization of reports to get cross-channel, but maybe that's OK. -- GitHub Notification of comment by csharrison Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/14#issuecomment-1130065900 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 May 2022 14:08:00 UTC