Re: [w3ctag/design-reviews] First-Party Sets (#342)

Hi TAG! 

We wanted to provide you with some updates:

- We are renaming "First-Party Sets" to "Related Website Sets", which we think better reflects its purpose. We have begun to gradually update relevant artifacts.
- We have increased the "Associated Subset" domain limit slightly from **three** to **five**, in response to [industry feedback](https://github.com/WICG/first-party-sets/issues/93). More on this choice [here](https://developer.chrome.com/blog/related-website-sets/#associated-domain-limit-increased-to-five-domains). 
- The feature has now been [rolled out](https://groups.google.com/a/chromium.org/g/blink-dev/c/7_6JDIfE1as/m/9uLnk0YwAQAJ) to 100% of Chrome stable users. As I mentioned in my last comment, we had previously paused the rollout due to some regressions caused by our implementation to prevent [privacy leaks on list changes](https://wicg.github.io/first-party-sets/#prevent-leaks). We have now resolved that issue, but have a remaining race condition in the Chromium implementation which occurs exceptionally rarely in practice - in those rare scenarios, if a URL is on a the list of sites whose data needs to be cleared due to a set membership change and that URL is loaded during startup, those loads might complete before we've cleared data. We are tracking this issue [here](https://bugs.chromium.org/p/chromium/issues/detail?id=1488079).


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

Message ID: <w3ctag/design-reviews/issues/342/1743033236@github.com>