Don Marti

The other side of this issue is that this proposal now relies on people using their public GitHub profile to review and comment on proposed sets. (The original version had...

A pre-defined numeric limit is always going to be too high for some use cases and too low for others. Some very small sets probably present the greatest risk of...

@jdcauley Viewability of a shared element could be a useful technical check. (A proposal for an associated set could include the ID of the element and a URL or hash...

There have been several issues related to ownership requirements in FPS. **Common data usage practices, not corporate owners, matter to users.** Many web users do not follow M&A news, so...

Three domains is already too many, if they're deceptive. It's fairly easy to think of some scams that could be pulled with two or three (https://github.com/WICG/first-party-sets/issues/101). Meanwhile, three might not...

Small affiliated sets are probably more of a risk than big ones because of the issue of reviewer time. (see https://github.com/WICG/first-party-sets/issues/101) A reviewer can deal with one large set faster...

(Updated to simplify) The privacy policy that is shared with users (which sites typically do by adding a regular link to at least the home page, possibly other pages) needs...

@RussStringham Good point. If the privacy policy is available in multiple languages * All FPS member sites should make the same languages available * Corresponding text for each language should...

@jwrosewell You mention that your proposed changes to First Party Sets would not require an Independent Enforcement Entity (IEE) but it is still not clear from this PR how the...

@jwrosewell Thank you for the answer. So I'm not clear where "validated" comes in in the proposal title. Sites can make claims about compliance with a particular law. It doesn't...