- From: Alex Cone via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Mar 2022 21:29:25 +0000
- To: public-patcg@w3.org
So it seems the second half to the original Issue question of 'Why would notice and consent not be adequate" is: >2. As a mechanism on top of the status quo of cross-site/app identifiers that haven't all gone away yet? I base this interpretation of your indirect reply directly above on the following quote from your reply directly above (emphasis mine): >James R:thanks! Regarding consensus about new APIs. **Not clear what the problem is with existing APIs.** Discussing some of the very largest companies, but not the majority of participants in this group, and those larger companies are engaging in more groups. At w3c, believe **we should use existing functionality / lego bricks**. Proposals from different browsers or gatekeepers tend to play to their functionality/advantage. **Not clear why we need to make any change from existing APIs.** If my interpretation is correct then it seems your intention for this Issue was to propose this group focus on a notice and consent mechanism for existing APIs (I presume third party cookies?) and _not_ whether any net new purpose limited APIs, like IPA for example, should be subject to best practices and legal requirements as far as user-level transparency and control mechanics go. Regarding the latter, I don't see anyone objecting to making new APIs subject to best practices and legal requirements as far as user-level transparency and control go. So if the intent behind the issue was about notice and consent on top of existing web APIs I believe you should say this plainly (without making people dig through minutes and make further inference). I think a lot of the back and forth of this thread could have been avoided. -- GitHub Notification of comment by alextcone Please view or discuss this issue at https://github.com/patcg/proposals/issues/5#issuecomment-1067314314 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 March 2022 21:29:27 UTC