Live data from Hacker News

Modifications to Google Chromium for removing Google integration

github.com

1–10 of 326 posts

Re: Modifications to Google Chromium for removing Google integration

#3
Coincidentally I had found out this one today and compiled it myself after a frustrating experience with `brew install chromium` (videos wouldn't play; inputs would blink).

I guess this has more flags set up by default, and it makes it easier to target a stable commit to compile against.

Also as a word of caution, don't use ungoogled-chromium binaries - they never are fully official/confirmed/reproducible. Running opaque blobs from strangers defeats the purpose of leaving Chrome for increasing privacy.

Just bite the bullet and run the 2h compilation process yourself.

Re: Modifications to Google Chromium for removing Google integration

#8

You could always switch to Firefox and use something like fastmail or protonmail. Did that a year ago, and actually it works better on mobile imo

protonmail sells your email for profit. I would better recommend fastmail which charges you, but it is still in unsafe legal regulation. You are not safe from the "lawful" dragnet neither.

Re: Modifications to Google Chromium for removing Google integration

#9
post #3

Coincidentally I had found out this one today and compiled it myself after a frustrating experience with `brew install chromium` (videos wouldn't play; inputs would blink). I guess this has more flags set up by default, and it makes it easier to target a stable commit to compile against. Also as a word of caution, don't use ungoogled-chromium binaries - they never are fully official/confirmed/reproducible. Running op…

Is there a flag for compiling out integrated login?

Re: Modifications to Google Chromium for removing Google integration

#10
post #3

Coincidentally I had found out this one today and compiled it myself after a frustrating experience with `brew install chromium` (videos wouldn't play; inputs would blink). I guess this has more flags set up by default, and it makes it easier to target a stable commit to compile against. Also as a word of caution, don't use ungoogled-chromium binaries - they never are fully official/confirmed/reproducible. Running op…

> Also as a word of caution, don't use ungoogled-chromium binaries

Unless you’re reading every line of code yourself before compiling it, I’d say you’re no safer going you’re route than downloading the binaries offered from the same source.

Post reply on HN