Re: [w3ctag/design-reviews] Design review of SameParty cookie attribute (#595)

@torgo Thank you for taking a look at this proposal! I'd like to point to [support from Edge](https://github.com/privacycg/proposals/issues/17#issuecomment-638996943), and [support to adopt in PrivacyCG from Safari](https://github.com/privacycg/proposals/issues/17#issuecomment-638689338). First-Party Sets is currently under discussion in PrivacyCG, and the `SameParty` cookie attribute was also discussed there. The result of the `SameParty` discussion is cfredric/sameparty/issues/2

My impression was that we had responded to the issues raised on #342, but perhaps we need to articulate that better back on that thread? Here is my enumeration of our response to the various issues:

* Mozilla's concern around self-declared vs. curated lists (in comparison with Firefox's use of [disconnect-entitylist.json](https://github.com/mozilla-services/shavar-prod-lists/commits/master/disconnect-entitylist.json)) were addressed in the rewrite of the proposal with the [UA Policy](https://github.com/privacycg/first-party-sets#ua-policy) section.
* Preventing use of First-Party Sets as a cross-site tracking vector is addressed in [this section](https://github.com/privacycg/first-party-sets#cross-site-tracking-vectors).
* We propose to aid user understanding via [UI Treatment](https://github.com/privacycg/first-party-sets#ui-treatment).
* We are considering options for enforcement against creation of excessively large sets in privacycg/first-party-sets/issues/29



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/595#issuecomment-768520874