Instead you have to follow some awkward workarounds, such as downloading a CRX manually and dragging and dropping it onto the extensions tab.
#INSTALL EXTENSIONS UNGOOGLED CHROMIUM INSTALL#
For example, removing all the Google code means you don't have the Webstore plugin, so can't install extensions from the store. This has some very far-reaching consequences.
Add, modify, or disable features that inhibit control and transparency (these changes are minor and do not have significant impacts on the general user experience). Strip binaries from the source tree, and use those provided by the system or build them from source. Disable or remove offending services and features that communicate with Google or weaken privacy. To fix this, ungoogled-chromium uses "a set of configuration flags, patches, and custom scripts" to do the following: Even the final build output includes some pre-built binaries." Furthermore, the normal build process for Chromium involves running Google's own high-level commands that invoke many scripts and utilities, some of which download and use pre-built binaries provided by Google. "A number of features or background services communicate with Google servers despite the absence of an associated Google account or compiled-in Google API keys. You thought Chromium did that anyway? So did we, but the "ungoogled-chromium" developer says: 
Ungoogled-chromium is a Chromium variant "for removing Google integration and enhancing privacy, control, and transparency".
0 kommentar(er)
