Re: [private-measurement] Request for help on multiple TAG reviews on measurement APIs (#22)

Yes, it's a good call-out @torgo, thank you. The unfortunate reality is that we are trying to build replacements for extremely mature technology (3PCs) that prop up huge #s of use-cases with barely any platform involvement needed (just placing a `<img>` tag, etc). Doing this in _private_ manner means that it's difficult to design something similarly simple (from the platform POV) - we need to be intimately aware of the data flows, computations, etc. This presents a challenging trade-off between privacy, the # of supported use-cases, and complexity.

That being said, we have been considering developer complexity as a principle when designing these things: the recent discussion in the PATCG at TPAC explicitly calls out developer ergonomics / complexity in a few of the comparison rows [here](https://docs.google.com/document/d/1oMe3Q7DMG3xzl-peIdq6voVD4PKD822-W4nf4ak7s2E/edit) that we discussed (see "Ease of advertiser adoption").



-- 
GitHub Notification of comment by csharrison
Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/22#issuecomment-1739338535 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 28 September 2023 14:20:34 UTC