This breaks captive portal detection, but captive portals still work.Disable intranet redirect detector (extraneous DNS requests).
Disable automatic formatting of URLs in Omnibox (e.g. (See docs/design.md for details on the system.) It currently supports many Linux distributions, macOS, and Windows. Add a custom cross-platform build configuration and packaging wrapper for Chromium. Add Omnibox search provider "No Search" to allow disabling of searching. Add more URL schemes allowed to save page schemes. Add Suggestions URL text field in the search engine editor ( chrome://settings/searchEngines) for customizing search engine suggestions. See docs/flags.md for the exhaustive list. Add many new command-line switches and chrome://flags entries to configure new features (which are disabled by default). These are the non-essential features introduced by ungoogled-chromium. Strip binaries from the source code (known as binary pruning see docs/design.md for details). In other words, no connections are attempted to the qjz9zk domain. This feature is implemented by replacing many Google web domains in the source code with non-existent alternatives ending in qjz9zk (known as domain substitution see docs/design.md for details), then modifying Chromium to block its own requests with such domains. This feature is a fail-safe measure for the above, in case Google changes or introduces new components that our patches do not disable. Block internal requests to Google at runtime. This includes disabling Safe Browsing. Google Host Detector, Google URL Tracker, Google Cloud Messaging, Google Hotwording, etc.) Disable functionality specific to Google domains (e.g. These are the core features introduced by ungoogled-chromium. For more detailed information, it is best to consult the source code. This section overviews the features of ungoogled-chromium. For more details, consult the Design Documentation. These features are implemented as configuration flags, patches, and custom scripts. 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). Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible. 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. Help is welcome! See the docs/contributing.md document for more information. A lightweight approach to removing Google web service dependency
0 kommentar(er)
