Anyone know when main/related_website_sets.JSON is deployed to chrome ?`

[Przemyslaw Jaskierny]

Hi All, 

 our configuration was merged into https://github.com/GoogleChrome/related-website-sets/blob/main/related_website_sets.JSON on last Tuesday but till now (Friday) we do not see changes in chrome chrome://system/#Related%20Website%20Sets. 

Thus, we are not able to do tests and work with RWS. 

Do anyone knows how flow looks like? When changes will be deployed to chrome?

best regards

Przemyslaw 

[Chris Fredrickson]

Per https://github.com/GoogleChrome/related-website-sets/blob/main/RWS-Submission_Guidelines.md#browser-behavior, you should expect Chrome clients to receive the updated list in 2 weeks or so. We (Chrome) do not make more precise guarantees than that, because Chrome ships the RWS updates in a staged manner for safety/stability reasons.

However, please do not use the official GitHub repository to test your set. The sets contained in the repository are shipped to every Chrome client, which takes real disk space and processing power on users' devices. Additionally, it would take some time to revert a RWS declaration if you discovered a problem with it during testing, as you can see. Sets should only be submitted to the public repository after you have tested them and you are certain that those are the changes you want every Chrome user to have.

You can test a Related Website Set locally, before you submit it to the public repository, by following the instructions here: https://developers.google.com/privacy-sandbox/3pcd/related-website-sets-integration#how_to_test_locally