- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Feb 2022 16:18:10 +0000
- To: public-patcg@w3.org
@medicinalcocaine3434 the document was using suggested edits and comments, it was with suggested edits that the document was defaced. @santirely if you take a look at the technical proposal, you'll find details on your question. Briefly: > Where would the match keys be stored in the device / browser / OS? We are proposing a new _read-only_ API, which the browser/OS would expose. > Could we adapt this solution so that it isn't so dependent on companies with a "large footprint"? Any website/app is able to write a match key, so it's not dependent on any set of companies. However, the more cross-device coverage a given companies match key has, the more accurate attribution that uses that match key will be. > What happens if suddenly Facebook or Google decide they'll only share their match keys with companies that play well with them? We are proposing that any site/app be able to reference any match key. Match keys are not shared, and the ability to reference them is not controlled by the companies that set them. -- GitHub Notification of comment by eriktaubeneck Please view or discuss this issue at https://github.com/patcg/proposals/issues/2#issuecomment-1039279184 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 February 2022 16:18:11 UTC