>So, if that is a correct assessment, although this bug report will technically solve itself with time (insofar as it is targeted at Floc)
If this closed, someone will open another report in the future >All in all, apparently Floc is being phased out we have a moving target. we will still keep an eye for future tracking mechanisms inside Chromium, under whatever name they may come to be. It's perfect decision to keep an eye on them and try to keep the chromium browser free from tracking mechanisms & data collection possibilities. Some browsers come with privacy model at first but later change to business models or add third-party services, additional features, closed-source parts, domains connectivities etc or delay release updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1926218 Title: Disable or Remove FLoC features and the provider service Status in chromium-browser package in Ubuntu: Triaged Bug description: Disable or remove entire FLoc, - FLoC component - Any other FLoC functionalities shipped in Chromium - FLoC client-side determinations of cohorts - Any reporting of FLoC cohort determinations to Google (or otherwise) servers (i.e., the reporting used for k-anonymity cohort protections) - FLoC JS methods (i.e. document.interestCohort) Brave, Vivaldi, Bromite have addressed FLoC issue and edge browser has disabled it Resources: https://github.com/brave/brave-core/pull/8468 https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/696632 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1926218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
