Opera is fine. Chinese connection doesn't bother me.
Modifications to Google Chromium for removing Google integration
61–70 of 326 posts
Re: Modifications to Google Chromium for removing Google integration
#62Coincidentally 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…
Wasn't the compiled-from-source chromium also downloading binary blobs without telling the user? There was an advisory about chromium doing it awhile ago.
Chromium suddenly starts downloading a binary blob
https://lwn.net/Articles/648392/
Re: Modifications to Google Chromium for removing Google integration
#63Rather just use Firefox. Its an insanely good browser.
Yes. But I presume the de-Google'd Chrome will still run most Chrome extensions, yes?
Re: Modifications to Google Chromium for removing Google integration
#64Earlier quoted context omitted.
That's a pretty significant issue. "Oh, it's a great browser! No, it doesn't work on 95% of computers."
but it only needs to work on _your_ computer (or whoever you're making the recommendation to).
The problem for me is that no one I know has a mac (I think their market share is like 10 percent). It's too expensive for many of the people I know and the rest play video games so they can't use a mac.
Re: Modifications to Google Chromium for removing Google integration
#65Earlier quoted context omitted.
>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…
> I don't think that's the best use of everyone's time or energy. Seems like there's a simple solution to this dilemma. Assuming build time is the single determining factor: If the value of two hours' build time overnight is less than the value of a privacy-enabled build of Chrome, then build Ungoogled Chromium overnight. Else, get Firefox.
Sure, that's a solution if you think that running their binary is unacceptable. But that's begging the question.
Most people running macOS (as vemv at least is) run a lot of random binaries from various types of strangers – mostly proprietary applications, although there's also things like Homebrew cached binaries, 'curl | sh' installers, etc. Now, in this case downloading a binary isn't necessary, since there's the option of building it yourself. That's great, and it's definitely (somewhat) safer to build it yourself... but that doesn't make the binary less trustworthy than if that weren't an option. If building sounds like too much effort, you shouldn't automatically give up on using the program, but just fall back to your personal baseline policy for running binaries. And for a lot of people, for better or worse, I think that policy is fairly trusting.
Re: Modifications to Google Chromium for removing Google integration
#66Re: Modifications to Google Chromium for removing Google integration
#67If you want Chromium based browser - Opera or Brave seems the way to go.
Re: Modifications to Google Chromium for removing Google integration
#68Re: Modifications to Google Chromium for removing Google integration
#69If you want Chromium based browser - Opera or Brave seems the way to go.
+1 for Brave