- From: Charlie Harrison via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Feb 2022 21:55:38 +0000
- To: public-patcg@w3.org
Hey @bmayd, we don't discuss this in a lot of philosophical detail, but there are a few key points in our explainer: 1. We allow third parties to register events and receive reports in the first place. The "reporting origin" is allowed to be a party that is not the top level site (publisher, advertiser) 1. For event registration, we allow parties that are not directly present on the page to register their own events via HTTP redirects ([link](https://github.com/WICG/conversion-measurement-api/blob/main/EVENT.md#:~:text=be%20present%20on-,redirect%20requests,-.)). 1. We chose in the most recent proposal revision to give third parties independent privacy budgets ([link](https://github.com/WICG/conversion-measurement-api/blob/main/EVENT.md#reporting-cooldown--rate-limits)), and some discussion on the security issue [here](https://github.com/WICG/conversion-measurement-api/blob/main/EVENT.md#denial-of-service). -- GitHub Notification of comment by csharrison Please view or discuss this issue at https://github.com/patcg/proposals/issues/8#issuecomment-1035562796 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 February 2022 21:55:39 UTC