-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block Floc checks in Chrome/uBO #1553
Comments
Is this a POC(Proof Of Concept) ? We don't fix POCs. |
As per |
While this has Proof of Concept website from EFF, Google is rolling this out as we speak. |
This is a good opportunity to implement Permissions Policy(formerly Feature-Policy) support in uBO. |
These are way too likely to cause page breakage, since they are meant to abort JS execution midway:
Following solution probably is better, since I gather that websites will have to check for the existence of
The only issue is whether this is too often ineffective due to race condition. I do not have Chrome on my side and can't test this. Whoever is found to be part of the trial could try and report. Given this is a trial, not sure adding a specific setting in uBO to address this is a good idea at this point, there could be changes in the future which would require to re-work the setting. |
|
I suppose we could add it to the "uBlock filters -- Privacy" for now, that's the purpose of the list, to create privacy-related filters optimized for uBO. |
I am going to add a scriplet specifically for this purpose: This way |
Related issue: - uBlockOrigin/uBlock-issues#1553
Related issue: - uBlockOrigin/uBlock-issues#1553 This commit ensures FLoC is opt-in. The generic filter `*##+js(no-floc)` in "uBlock filters -- Privacy" ensures the feature is disabled when using default settings/lists. Users can opt-in to FLoC by adding a generic exception filter to their custom filters, `#@#+js(no-floc)`; or they can opt-in only for a specific set of websites through a more specific exception filter: example.com,shopping.example#@#+js(no-floc)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Would be great if this could be configurable via Advanced Config, such the the scriptlet for redefining Document.prototype.interestCohort isn´t executed. |
|
Should have called it floc-off :) |
https://github.com/jkarlin/topics
https://techcrunch.com/2022/01/25/google-kills-off-floc-replaces-it-with-topics/ |
Related feedback: - uBlockOrigin/uBlock-issues#1553 (comment)
Now we must follow Topic API, maybe community wrote draft for |
For years I've pointed out that Chrome is an adtech agent, not a user agent, however hard they try to spin it as the latter. This ever present motivation to have adtech API embedded in it just further illustrate that point. |
I don't think API needs to be foiled, as per the example, it needs to send a |
For all of this discussion of FLoC and v3 manifest, I would much prefer if @gorhill maintained a clear and visible recommendation of what browsers you should use. He does not owe anything to Google. And if he thinks other browsers are better I would love to see that in the README. |
Prerequisites
Description
Block FloC requests within uBO
A specific URL where the issue occurs
Test case:
https://amifloced.org/
But will eventually occur on various sites.Steps to Reproduce
https://amifloced.org/
Expected behavior:
uBO should block FloC for privacy.
Have an option to counter google's tracking. Would recommend a default option for Chrome, but if not available a configurable option.
Actual behavior:
FloC isn't being blocked in uBO.
Your environment
Maybe too generic, but something like this:
The text was updated successfully, but these errors were encountered: