xavier666

🦊🦊

You can fork it, fix it, do whatever you want with the code, but on the main chromium repo they rarely accept PRs from random contributors

This needs to be discussed more by the community.

I can kind of understand what's happening. They want to have complete control over what goes in an out of Chromium. Some PM is probably overseeing the PRs, and if some PR hinders their ability to collect data, that PR gets rejected. Mighty fine project this is. Other forks probably don't have the resources to go through all the commits issued by Google and just accept them as it is. They just makes the changes to suit their own agenda. All the more reason for people to switch to Firefox

I wonder how Ungoogled Chromium is affected by all this.

The code doesn't do anything on non-Google domains.

A Google engineer adds a piece of code, does not document what exactly it does, and it was approved without question. Something is seriously wrong with this or I don't know how the Chromium project works.

True. We can also not run code at all and be perfectly safe.

I wish there was a comparison. Number of 0days in open source and 0days in closed source for comparible projects and a measure for time to mitigate the 0days.

I am no expert on code-auditing. But I'm slightly at peace that there are 100s of experts looking at the code because it's open-source. But i also understand mistakes can still happen. It's not a perfect system, but it's the best solution so far.

Remember this thumb rule -> if it's not open-source, you are allowing the software to do whatever it wants to do.

No regulation, law, support group is going to help you. You are digging your own grave.

Those that try to hide or shift blame of mistakes are a bigger red flag in my book.

People, please; look at this.

It's inevitable that mistakes will happen.

I remember the good old times when testers has to check if their sites work on Chrome/Firefox/Opera/Safari/Edge.

And you could simply have a separate Firefox profile rather than spinning up an entire virtual machine.

This is what I do. Even though there is nothing wrong with the Qubes approach, I think it's overkill unless you are hiding from nation-state attackers.

I gave up and used a Windows VM for such shenanigans. It's hard when even the government doesn't want to listen. This is a good project which bridges the gap -> https://github.com/Fmstrat/winapps.

The primary issues that I faced with Windows (Win10 nearly a decade ago) are

• very slow updates
• constant 100% disk usage after boot
• high background process usage
• [Rare] messing with my dual partition setup
• The final error which caused me to format my PC -> After logging in, the desktop froze, no icons showing up, no task manager.

If I had never used Linux, these wouldn't even seem like problem; just normal Windows shenanigans. But after using Linux, I can never go back. I don't know how much worse/better Win11 is now but can't be bothered to try.

For robotics and embedded system - My DIY or the highway