chromium VS ungoogled-chromium

Time to dig out my Wyse 50 again! https://chromium.googlesource.com/chromium/src/+/HEAD/docs/o...

Thanks. Yes, rendering and shaping are distinct but some of the linked libraries did one, the other, or both and the parent commenter singled out rastering which is how I ended up putting FreeType and HarfBuzz in the same sentence. Even then both are commonly used in tandem (see [1]-[9]) and have a few overlapping functionalities.

> it does support BiDi, complex script shaping

Hey, that is indeed quite good. Would you mind if I ask you how well is the support for popular Asian languages?

> linking C and Rust in WASM is unfortunately not really possible

Damn. I am not very experienced in Rust but I would not have guessed that. I apologize if I misrepresented difficulties related to targeting WASM.

[1] https://github.com/apple-oss-distributions/WebKit/tree/WebKi...

[2] https://github.com/apple-oss-distributions/WebKit/tree/WebKi...

[3] https://github.com/chromium/chromium/tree/main/third_party/f...

[4] https://github.com/chromium/chromium/tree/main/third_party/h...

[5] https://searchfox.org/mozilla-central/source/modules/freetyp...

[6] https://searchfox.org/mozilla-central/source/gfx/harfbuzz

[7] https://cs.android.com/android/platform/superproject/+/maste...

[8] https://cs.android.com/android/platform/superproject/+/maste...

[9] https://www.amazon.com/gp/help/customer/display.html?nodeId=...

The word "Zygote" will actually be really clear to anyone who's been exposed to Chrome's multiprocess architecture.

https://chromium.googlesource.com/chromium/src/+/HEAD/docs/l...

> A zygote process is one that listens for spawn requests from a main process and forks itself in response. Generally they are used because forking a process after some expensive setup has been performed can save time and share extra memory pages.

With that background, --zygote isn't actually a flag at all. If you click on it it takes you to a string constant, but that string is actually a value for the --type flag. e.g. an unsandboxed zygote process would have `--type=zygote`.

`--type` is itself an internal flag, explaining it's lax description of "Flags spied upon from other layers.". However it is briefly described in the documentation I linked above.

Chromium license is permissive: https://github.com/chromium/chromium/blob/main/LICENSE

I recently found a degoogled version of chrome.on GitHub. It does have changes to it besides removing all the links to Google services. So it hopefully will keep adblockers intact. https://github.com/ungoogled-software/ungoogled-chromium

Ungoogled chromium may be another good choice. I use it on one of my Debian VMs which has 2 gigs of ram; takes ~180M ram with a couple tabs open.

Ungoogled chromium is it's on browser https://github.com/ungoogled-software/ungoogled-chromium There is plans to add more browsers sometime

Release upgrades are much more complex than simply upgrading your system. This is not ArchLinux. Debian is a release based distro. Packages get dropped, packaged get changed. You may also install an application out of the debian repo like Codium or Ungoogled Chromium or simply have various foreign packages in your system from other applications or personal modifications of packages like i like doing and sometimes forget i have.

At the very least you would use this

If you like the chromium experience and the only drawback for you is the lack of privacy, then you should probably try Ungoogled Chromium: https://github.com/ungoogled-software/ungoogled-chromium . If you choose this browser you can download it from here: https://ungoogled-software.github.io/ungoogled-chromium-binaries/

Some realistic things that people can do without affecting their online usage: - Use temporary emails if you don't want to give your real email to a website, but must enter one to access the page/asset. - Use email alias services like SimpleLogin, or Firefox Relay to create email alias for your social media/other accounts. - Don't use voice/video chat features on your browser? Disable WebRTC, it is known to leak your IP address, or use a VPN if you must. But don't use a VPN if you don't need one. - On your router, block access to Google's DNS (some apps will use DoH to connect to their DNS), and change your primary DNS to Quad9, or AdGuard. Or configure NextDNS for your own use case. If you don't have blocking feature on your router, you should be able to use routing rules to forward any traffic to Google's DNS to 0.0.0.0. - If you need extra blocking features, look at RethinkDNS app/website to configure your own block lists. - Use Firefox and configure the security/privacy policies as you need. If you don't want that, use Ungoogled Chromium. If you want to use Firefox, but don't know how to secure it any further than what's enabled by default, use LibreWolf. - Use Bromite on Android instead of Chrome. Bromite offers some blocking capabilities, which Chrome doesn't. You can also use Firefox and install uBlock Origin. - Whenever you install a new app, don't just give access to everything it asks for without considering if the app really needs that access. For instance, if you install a game, but you know that you won't be using voice features, don't give it access to your microphone. It may sound trivial, but some apps ask for contacts, sms, storage, internet, camera, etc. even if they shouldn't be accessing any of those. - Disable background data usage for non-critical apps. - Search and use debloating guides specific for your Android manufacturer and Windows to disable unnecessary apps. - Don't use free VPN apps unless it is a well known player in the field, like AdGuard, Proton etc. - Before install any app using APK source, always scan it online using virustotal.