Live data from Hacker News

Modifications to Google Chromium for removing Google integration

github.com

11–20 of 326 posts

Re: Modifications to Google Chromium for removing Google integration

#11
post #2

Google Chromium, sans integration with Google, and sans updates. Thanks but no thanks.

>"IMPORTANT: These binaries are provided by anyone who are willing to build and submit them. Because these binaries are not necessarily reproducible, authenticity cannot be guaranteed."

Safety not guaranteed. Just how I like my browser.

Re: Modifications to Google Chromium for removing Google integration

#12
post #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.

Could you please provide a citation for your first claim that ProtonMail sells your email for profit? Their entire sales pitch heavily revolves around clientside decryption that should in theory prevent this from being possible; I'd very much like to know if this is not the case.

Re: Modifications to Google Chromium for removing Google integration

#13
post #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.

[deleted]

Re: Modifications to Google Chromium for removing Google integration

#14
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.

Generally as a software developer I can assess which projects' source to trust, else I wouldn't be running thousands of transitive dependencies in my machine.

Binaries which are unofficial to even ungoogled-chromium itself surpass my threshold of trust.

But yes, one could take a further step and extract the interesting bits from this project and apply them to the official Chromium trunk.

Re: Modifications to Google Chromium for removing Google integration

#15
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.

In spirit I'm with you but somebodies bound to do it and that alone makes it safer to compile from publicly provided source.

Re: Modifications to Google Chromium for removing Google integration

#16
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…

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

I don't think that's the best use of everyone's time or energy. Not to mention, it may be more error prone, or even insecure depending on what your base system is like. And you'll have to track updates. It seems like chromium is problematic to build in general. Debian hasn't marked it as reproducible. It is also not clear if it is possible to build it for Android using a Foss stack. Various efforts to include chromium or derivatives in Fdroid have failed.

Re: Modifications to Google Chromium for removing Google integration

#17
C'mon. People are trying to stand up to Google. It's important to encourage this behavior, or at least not spread FUD with unsubstantiated claims of insecurity.

EDIT: Lol, Google employees swarming HN on a Sunday. I guess people are getting a little nervous that a mass exodus from Chrome might be beginning.

Hey look ma, an unsubstantive complaint about downvotes! Can't wait for my account to be penalized further.

Re: Modifications to Google Chromium for removing Google integration

#19
This seems like one of the most difficult solutions to the problem of switching to a browser that's not Chrome.

Not only are there other browsers like Firefox and Safari, but there are other Chromium-based browsers like Vivaldi and Opera.

I would have liked to read about some expected use-cases in the readme.

Post reply on HN