Has nobody bothered to read anything about FLoC? The purpose of this permission is to prevent embedded third-party content from using FLoC. Besides that it’s a no-op. 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…
>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.
Who's to say how this evolves in the future?