Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Modifications to Google Chromium for removing Google integration

github.com

Post reply on HN
Print view View original

261–270 of 326 posts

Re: Modifications to Google Chromium for removing Google integration

#261

Post by def_true_false »

mythz wrote: post #84

My preference for a well supported Chromium-based browser that's not Chrome would be to use one of the "Blink" based browsers: https://vivaldi.com https://brave.com https://www.opera.com Opera was purchased by a Chinese consortium, I'm not a fan of Brave's hijacking of ad spaces so my preference is currently vivaldi - which was founded by co-founder and former CEO of Opera and has been adding new innovative features…

Many features that made Opera great still don't work in Vivaldi - last time I checked, RMB+wheel tab cycling was completely broken. When it works, the UI is slow and laggy.

Going from old Opera to Vivaldi feels like switching from Sublime to some Electron garbage.

Re: Modifications to Google Chromium for removing Google integration

#262

Post by yjftsjthsd-h »

sneak wrote: post #121
lettergram wrote: post #7

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

Switching email providers is of little use for privacy from Google when everyone you correspond with is also using Google.

And if everyone says that, then no one will ever leave.

Re: Modifications to Google Chromium for removing Google integration

#264

Post by nothrabannosir »

stonogo wrote: post #222
sneak wrote: post #121

Earlier quoted context omitted.

Switching email providers is of little use for privacy from Google when everyone you correspond with is also using Google.

This is a contentless argument, which I am tired of seeing parroted. I do business with hundreds of entities that do not use Google infrastructure. I have thousands of contacts whose email headers indicate usage of Exchange servers. It's not about your twelve friends who use GMail, or even your hundred GitHub collaborators who use GMail. It's about the entire rest of the Internet, which is still there, living happily…

And even if it weren't, it's an unconstructive, defeatist style of thinking which does not engender positive change in society, but fosters local maxima.

For every person who does not think this way, society is better off.

Re: Modifications to Google Chromium for removing Google integration

#265

Post by pythonaut_16 »

bad_user wrote: post #243

If you're using "Ungoogled" Chromium, you're still contributing to Chrome's monopoly and you're still helping Google's dominance of the web. Chromium may be open source, but its development is controlled by Google. Unless you have Google-like resources available, you won't be able to create a meaningful fork that your less technically savvy users can benefit from. "Ungoogled" Chromium is a trap. Use another browser.…

The user isn't the problem, the developer is.

If you're developing against Chrome/Chromium, particularly "works in Chrome" instead of developing against the published Web standards, you're support Google & Chrome.

Re: Modifications to Google Chromium for removing Google integration

#266

Post by kalcode »

dedsm wrote: post #213

Since quantum arrived, firefox developer edition is my browser of choice, and with the containers functionality it checks all my marks.

Problem is when something crashes on Firefox it still tends to take everything with it. This is very annoying when developing something. Often when you have bad code as you are creating or changing things.

So for developing I still prefer Chrome. Besides that Firefox since quantum been very nice.

Re: Modifications to Google Chromium for removing Google integration

#267

Post by ascar »

MaxBarraclough wrote: post #226
simias wrote: post #211

Earlier quoted context omitted.

It's not about meticulously reviewing every commit for every project that I use, obviously nobody has time for that. For me the most important part is being able to fork the project if you want to add features or are unhappy with the way the original project is going, you don't merely have to beg the maintainers to add a certain feature, you can do it yourself. And perhaps more importantly I'm not screwed if, for one…

Also, simply making the source-code visible to all, helps keeps the honest guys honest. That's true even if the licence isn't truly Free and Open Source. No-one dares to commit spyware to GitHub.

> No-one dares to commit spyware to GitHub.

I see where you are coming from, but this is simply not true. You can argue nobody concerned with his own reputation commits spyware to a public repo, but malicious actors are usually not concerned with that or try to stay anonymous in the first place.

Here is a recent example of malicious commits to a github repo: https://news.ycombinator.com/item?id=17458329

Re: Modifications to Google Chromium for removing Google integration

#268

Post by Iolaum »

foxX wrote: post #257
MaxBarraclough wrote: post #226

Earlier quoted context omitted.

Also, simply making the source-code visible to all, helps keeps the honest guys honest. That's true even if the licence isn't truly Free and Open Source. No-one dares to commit spyware to GitHub.

The fact that the source code is available does not guarantee that the blob is the product of that source.

That's true and, to me, has been brought on the spotlight from Microsoft practices around VSCode. On the other hand, for an OSS project, building the binary is not that hard.

Re: Modifications to Google Chromium for removing Google integration

#269

Post by zlatan_todoric »

TekMol wrote: post #255
zlatan_todoric wrote: post #233

Earlier quoted context omitted.

Debian gets sponsored by various ways but the money isn't used directly for developers nor their time. It is volunteer based project and money is usually used for hardware, sprints, conferences, outreachy etc. That said Debian does take it seriously when it comes to privacy and security so you can always report bugs on such. Do note that Debian's Chromium builds have always disabled the infamous "mic always on" optio…

it should be much easier to contribute to Debian now But aren't they constantly getting new versions of Chromium from Google? I think going into the Debian Repo of Chromium and changing it would not be a viable path, right? You either have to convince Google to accept your changes too (Good luck with them accepting the de-googling haha) or you would have to consider a life of constantly de-googling new versions of Ch…

Debian maintains its set of patches often (quite easy to handle with quilt in debian/patches). We get upstream source from upstream of course and use our patches until they get accepted (we don't force upstream to do so) when we of course remove obsolete ones.
Post reply on HN