<story><title>Opting Your Website Out of Google&apos;s FLoC Network</title><url>https://paramdeo.com/blog/opting-your-website-out-of-googles-floc-network</url></story><parent_chain><item><author>jahewson</author><text>Has nobody bothered to read anything about FLoC?&lt;p&gt;The purpose of this permission is to prevent embedded third-party content from using FLoC. Besides that it’s a no-op.&lt;p&gt;FLoC does not track arbitrary websites, it tracks sites which retrieve the FLoC cohort via JS. So instead of dropping a unique third party cookie, and associating it with the data on the page, sites can now retrieve a k-anonymous cohort id and associate it with the data on the page. If you’re not doing that (or serving ads) there’s nothing you need to do.&lt;p&gt;That’s not to say that FLoC doesn’t deserve criticism just that most criticism I’ve encountered is not grounded in reality.</text></item></parent_chain><comment><author>jedwhite</author><text>According to the W3C Federated Learning of Cohorts
Draft Community Group Report, 13 April 2021, Paragraphs 3 &amp;amp; 7.1.1:&lt;p&gt;&amp;quot;The interest cohort API lives under the Document interface since the access permission is tied to the document scope, and the API is only available if the document is in secure context.&amp;quot;&lt;p&gt;and&lt;p&gt;&amp;quot;The page can opt itself out of the interest cohort computation through the &amp;quot;interest-cohort&amp;quot; policy-controlled feature. [PERMISSIONS-POLICY]&amp;quot; [1]&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;wicg.github.io&amp;#x2F;floc&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;wicg.github.io&amp;#x2F;floc&amp;#x2F;&lt;/a&gt;&lt;p&gt;Edit for para reference.</text></comment>
<story><title>Opting Your Website Out of Google&apos;s FLoC Network</title><url>https://paramdeo.com/blog/opting-your-website-out-of-googles-floc-network</url></story><parent_chain><item><author>jahewson</author><text>Has nobody bothered to read anything about FLoC?&lt;p&gt;The purpose of this permission is to prevent embedded third-party content from using FLoC. Besides that it’s a no-op.&lt;p&gt;FLoC does not track arbitrary websites, it tracks sites which retrieve the FLoC cohort via JS. So instead of dropping a unique third party cookie, and associating it with the data on the page, sites can now retrieve a k-anonymous cohort id and associate it with the data on the page. If you’re not doing that (or serving ads) there’s nothing you need to do.&lt;p&gt;That’s not to say that FLoC doesn’t deserve criticism just that most criticism I’ve encountered is not grounded in reality.</text></item></parent_chain><comment><author>aww_dang</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;WICG&amp;#x2F;floc&amp;#x2F;issues&amp;#x2F;82&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;WICG&amp;#x2F;floc&amp;#x2F;issues&amp;#x2F;82&lt;/a&gt;&lt;p&gt;&amp;gt;During the current FLoC origin trial, a page will also be included in the calculation if Chrome detects that the page load ads or ads-related resources.&lt;p&gt;Who&amp;#x27;s to say how this evolves in the future?</text></comment>