Ungoogled-Chromium

[labbe5]

To get your copy of ungoogled-chromium : https://ungoogled-software.github.io/un ... -binaries/

AppImage and deb available for 64-bit systems.

ungoogled-chromium retains the default Chromium experience as closely as possible. Unlike other Chromium forks that have their own visions of a web browser, ungoogled-chromium is essentially a drop-in replacement for Chromium.

From a technical standpoint, ungoogled-chromium is a set of configuration flags, patches, and custom scripts. These components altogether strive to accomplish the following:

Disable or remove offending services and features that communicate with Google or weaken privacy
Strip binaries from the source tree, and use those provided by the system or build them from source
Disable features that inhibit control and transparency, and add or modify features that promote them (these changes will almost always require manual activation or enabling).
Source : https://github.com/Eloston/ungoogled-ch ... t-packages

[RetroTechGuy]

Thanks Labbe! I suspect that will also make the browser "less heavy" (so many of these modern browsers pull virtually any machine right to its knees)

[mikeslr]

Hi all,

Downloaded both the AppImage and the Portable. ldd shows no missing dependencies on the latter. Neither, however, would run. So I'm guessing that they would have to be "adjusted" to run as Spot.

At 88 Mbs the AppImage is larger than the current Google-Chrome70-64.sfs. The portable, before extraction was 63. Since I couldn't run them, I have no idea what their demands on RAM would be.

[Null_ID]

Hi all,

Downloaded both the AppImage and the Portable. ldd shows no missing dependencies on the latter. Neither, however, would run. So I'm guessing that they would have to be "adjusted" to run as Spot.

At 88 Mbs the AppImage is larger than the current Google-Chrome70-64.sfs. The portable, before extraction was 63. Since I couldn't run them, I have no idea what their demands on RAM would be.

Something that I'd like to point out to all whom it may concern:

The appimage most definitely works in XenialPup 7.5. To make this happen, you must give executable rights to the appimage from Properties, then boot the appimage from terminal and issue the "--no-sandbox" command line switch on startup to make UGC dismiss the check for user privileges. You should now have a working browser. Since we're messing with command live switches here, I'd also throw in "--incognito" for good measure.

[8Geee]

Isn't this like "iron"?, or is that just the browser portion?

Regards
8Geee