- From: Alex Cone via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2022 18:01:54 +0000
- To: public-patcg@w3.org
First, I believe @benjaminsavage's strawperson and the incorporated updates suggested by @martinthomson are a very defensible position to begin with. Second, like @benjaminsavage, I believe some affordance should be made here on the part of the browser maker to demonstrate the system they are a part of (if/when these APIs are generally available), which hopefully becomes part of powering a multi-billion dollar/euro/etc industry, is a transparent actor. The ask @benjaminsavage is making here is like he says "a pretty low bar," but I think the concession is an important one. We don't have to talk about self-preferencing in browser or OS companies to stipulate that the standard we are developing here has openness for all parties involved in making the API(s) work for software developers and ultimately the better data protection and privacy of end users. -- GitHub Notification of comment by alextcone Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/17#issuecomment-1163444761 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 June 2022 18:01:56 UTC