-
Notifications
You must be signed in to change notification settings - Fork 877
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
Does Ungoogled Chromium include FLoC code? #1474
Comments
The code exists, but field trials should not be active unless your version of chromium was built with It also seems to (in it's current implementation) check It might be a bit too early to implement a patch right now to remove this since there will likely be a lot of changes to this code in the upcoming releases, but it wouldn't be too difficult to implement a patch before it becomes enabled by default. Extra info: That EFF article only links the component part to floc, the rest is here There is a Google blog post here that goes into more detail about the trial. |
Has this been confirmed? |
Just wanted to add my vote for either removing or disabling this "feature" |
Seems like Vanadium has patched FLoC, the fix seems applicable to Ungoogled Chromium: Can we please have the same fix in Ungoogled Chromium? |
Are you tracking differences between UG & Vanadium? I'm curious about that too - and wonder if the projects can help deduplicate each others efforts. |
According to https://amifloced.org/ last ungoogled chromium (89.0.4389.114) does not have FLoC enabled: |
That may be normal, because I think that all Chrome Users don't have Floc enabled either. |
What is the current situtation and plan for the FLOC removal? |
I've had a patch ready for a while that disables the current implementation, but I've been waiting to see what changes get made before mid-July. So far it hasn't had as much activity as I thought it would have. I'll take some time this weekend to update the patch a bit and submit a PR afterwards. |
Thank you again for the patch. It seems like the Bromite project has failed to implement your patch, they seem to rely entirely on Google's preset conditions for FLoC being enabled. They see no necessity to explicitly patch this, and when I hinted at your patch in frustration, my comment got marked as "disruptive content" (well yes, that is correct, it is meant to "disrupt" the developer's lazy development attitude). If you can, please comment on why a patch is necessary in my stead: You don't have to, but seeing how you are the author of an applicable patch and since I would like to continue using Bromite on mobile, could you please help me out there in the interest of all Bromite users? Thank you. |
@Peacock365 You might be interested in this effort: #1395 |
Is the current FLoC origin trial included in Ungoogled Chromium? How will it be handled once trials are over and it's fully implemented and ready to go in Chromium? Sources mention the code for this trial made it into Chromium (and not just Chrome), and thus I would assume it would propagate downstream to this project. I searched the internet and this issue tracker, but found no mention of Ungoogled's stance on this controversial inclusion in Chromium.
https://www.eff.org/deeplinks/2021/03/google-testing-its-controversial-new-ad-targeting-tech-millions-browsers-heres
https://source.chromium.org/chromium/chromium/src/+/master:components/federated_learning/?q=federated%20learning&ss=chromium%2Fchromium%2Fsrc
WICG/floc#25
The text was updated successfully, but these errors were encountered: