3 ms·
Ask HN: Can the community remove Google FLoC from Chromium
I believe Brave and Vivaldia have announced that they will not use the Google FLoC features that Google have contributed to Chromium.
Some have raised concerns about having to maintain "their own fork" and means
extra work to synch up the main Chromium tree.
Is the reverse possible?
Can the community remove Google FLoC from Chromium itsel?
Tell Google to build it for Chrome?
Is there governance routines for it?
- kjjjjjjjjjjjjjj 6y agoSomeone makes a google-less build of chromium, so maintaining one fork would be the best option. However, your best option is to just use a browser that actually cares about your privacy life safari
- pajko 6y agoHere you are: https://chromium.woolyss.com/ https://chromium.woolyss.com/ Sources: https://github.com/Eloston/ungoogled-chromium https://github.com/Eloston/ungoogled-chromium
- twobitshifter 6y agoThanks, the FLoC discussion for ungoogled chromium is here: https://github.com/Eloston/ungoogled-chromium/issues/1474 https://github.com/Eloston/ungoogled-chromium/issues/1474
- deleted 6y ago[deleted]
- Trias11 6y ago+100
- brudgers 6y agoThe governance of Chromium is internal to Alphabet. Chromium is developed with Google Chrome in mind. The Chromium community consists of people working on things in the interests of Alphabet. There’s no consensus process for including stakeholders. Forking is the only option for making changes not to Alphabet’s liking.