31–40 of 264 posts
1. Another alternative is to run the proxy locally. I run a web proxy bound to the loopback.
Earlier quoted context omitted.
It seems not. The FLoC page ( https://web.dev/floc/ ) says: > For pages that haven't been excluded, a page visit will be included in the browser's FLoC calculation if document.interestCohort() is used on the page. 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.
Excluding a page is a manual process however, requiring to set the header mentioned in the blog post. So website owners have to explicitly opt-out of FLoC.
I think I will just block Chrome users from my websites
Waiting for google to make this a ranking factor for SEO like they did with amp.
How does it benefit website owners to opt out?
Let me get this straight: even if my site has no ads or trackers, Chrome will now use my visitors data for advertising and surveillance??? Does anyone else see FLoC as worse than the current state we're in?
Tell them it's time for the government to step in and remove Google's ability to run a browser.
Google cannot be allowed to continue running Chrome. They've abused this position time and time again to the detriment of us all.
Let me get this straight: even if my site has no ads or trackers, Chrome will now use my visitors data for advertising and surveillance??? Does anyone else see FLoC as worse than the current state we're in?
Perhaps someone will set up a remote^1 web proxy that adds the suggested "Permissions-Policy: interest-cohort=()" HTTP header to disable FLoC. Browser extensions are great but there is nothing to stop Google from removing access to them through the Play Store at any time. 1. Another alternative is to run the proxy locally. I run a web proxy bound to the loopback.
Add a simple header to block FLoC on your website (fortunately): `permissions-policy: interest-cohort=()` It's only deployed on a test set of Chrome browsers so far, and it does create a warning message on browsers that don't support it. [1] [1] https://stackoverflow.com/questions/66997942/error-with-perm... Edit to note support for blocking this!
That said, according to that StackOverflow page, the error only appears in DevTools. That's not as bad as it sounded at first. I was worried it would be an IE-style alert on page load, for example, or a visible bar across the top of the page. It's not, it's just spam in the DevTools console.
Let me get this straight: even if my site has no ads or trackers, Chrome will now use my visitors data for advertising and surveillance??? Does anyone else see FLoC as worse than the current state we're in?