On Thu, 11/14/2024 9:55 PM, Newyana2 wrote:
On 11/14/2024 4:34 PM, DanS wrote:
I typically use de-Googled Chromium...or I should say, never-Googled Chromium.
�� I use that, too, when I can't use Firefox. Though I'm not clear
about exactly how ungoogled it is. There's still the "Google
and you" section of the settings. And the UngC settings are the
same limited, obfuscated selection that Chrome has. So maybe
it doesn't call home to Google? Hopefully. But I still only use
it for specific special cases and then delete history, cookies, etc,
Chrome and Chromium are two different browsers.
Chromium = FOSS (the base code)
Chrome = Chromium + proprietary additions (closed source, binary only)
Google would not want the latter one source distributed, because
there could be API keys in there or the like.
A copy of Chromium is harder to find, at least I have
trouble trying to locate one when needed (there used to be
a capability, like Mozilla, to pick any older release, as you may
not want the latest one). While this looks promising, I'm not
going to stick a shovel in this right now.
https://www.chromium.org/getting-involved/download-chromium/
Chromium is the FOSS version. it is the "code base".
People outside Google can contribute to it.
Chrome is what you get, after the Google developers add
their tracking. Chrome is what you download from Google.
A copy of Chromium still has structures (like DOM storage),
which "arm" the web for doing naughty things. In a sense,
the Chromium design objective, of tracking people, don't
really diverge enough to cause Google any grief. DOM storage
is not exactly something the users were crying for (yet another
super-cookie).
But any additional mechanisms, the auto-tracking du jour
of the Google Corporation, for the most part that is
injected into Chrome, since the Chrome source (with
Google changes) is not available.
Whereas you can build Chromium from source if you want.
I believe I have done this here, because I was using it
to try to reproduce the USB stuttering problem in windows,
which the Chromium build environment can trigger.
You would think that running thousands of shell utilities
one after another (twelve copies of GCC in parallel is just
one example), would have no effect at all on a modern OS. However, on
modern Windows, the OS "slows down" the longer you do that
(that's what the Chrome developer in charge of optimizing
the build engine on Windows was complaining about).
"Real computers" do not slow down, when you run builds on them.
The machines have the same speed, every day, no matter how
many builds you have done.
Paul
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)