- From: Robin Berjon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Mar 2022 15:07:54 +0000
- To: public-patcg@w3.org
James, the best way for you to contribute constructively is to engage with the existing body of work that shows that consent does not, apart in rare cases, provide a sound basis for data protection or privacy. The purpose of this group is to develop private advertising technology. If consent worked for the kind of data processing required in advertising, we wouldn't actually need this group. The technology to produce prompts inside of browsers actually exists. Since consent doesn't work, we need better solutions. This isn't "concerning," it's just the conclusion that is supported by the evidence — as indicated to you over and over again. Repeating the same discredited argument without novel material is not constructive. That consent cannot provide a defensible approach for the kind of processing this group is working on does _not_ mean that this becomes the "Fixing Consent Community Group." You know what else doesn't provide a defensible approach for the kind of processing this group is working on? Bourbonnais donkeys. That doesn't mean we need to rename this group to the "Fixing Bourbonnais Donkeys Community Group." We just won't rely on Bourbonnais donkeys in the same way that we won't rely on consent. Claiming that we need to fix your pet preferred solution because it doesn't work isn't constructive. Making strawman arguments isn't constructive. Having to deal with reality isn't an "unjustified burden." But hey, if you have something actually _new_ and that you've somehow solved consent, then there's literally a couple of decades' worth of backlog in [APIs that we can't expose](https://www.w3.org/2011/07/DeviceAPICharter#deliverables) because relying on consent is unsafe. It would be a revolution in Web technology. -- GitHub Notification of comment by darobin Please view or discuss this issue at https://github.com/patcg/proposals/issues/5#issuecomment-1055543334 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 March 2022 15:07:56 UTC