#Chromium vs ungoogled chromium update#
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).Ībout the first concern I don’t know what to say: right now I use some unofficial binaries (still made by one of the contributor of the project) build for arch and I update them manually whenever, after a manjaro update, the previous version didn’t work anymore because some mismatch in the dynamic libraries (or if a new chromium version is released I, after testing, it still seams to work on my manjaro machine, otherwise i downgrade to the previous version).Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.
#Chromium vs ungoogled chromium code#
Remove all code specific to Google web services.Remove all remaining background requests to any web services while building and running the browser.Ungoogled-chromium addresses these issues in the following ways: In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations. However, Chromium still has some dependency on Google web services and binaries. Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. In scenarios where the objectives conflict, the objective of higher significance should take precedence. However, almost all of these features must be manually activated or enabled. ungoogled-chromium features tweaks to enhance privacy, control, and transparency.Unlike other Chromium forks that have their own visions of a web browser, ungoogled-chromium is essentially a drop-in replacement for Chromium. ungoogled-chromium retains the default Chromium experience as closely as possible.ungoogled-chromium is Google Chromium, sans dependency on Google web services.
In descending order of significance (i.e.
Fortunately now the Ungoogled Chromium team has an official repository on the Opensuse Build Service that automatically produce the binary for arch from their arch Github repo, so now porting this is just matter to push the update update from their repo to Manjaro’s ones when the dependencies of the browser are satisfied by the packages in the repo.įor anyone who doesn’t know what Ungoogled Chromium is, here is an extract from their main Github repo: ungoogled-chromiumĪ lightweight approach to removing Google web service dependency Objectives
Last time this package was requested the request was negated because there was no one willing to build every time a chromium fork (it is a very very long process).
0 kommentar(er)
