Modifications to Google Chromium for removing Google integration and enhancing privacy, control, and transparency with a new logo to recognize this version.
Pull request Compare This branch is 4 commits ahead, 280 commits behind Eloston:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
buildkit
developer_utilities
resources
.gitignore
.travis.yml
BUILDING.md
DESIGN.md
DEVELOPING.md
FAQ.md
LICENSE
README.md
buildkit-launcher.py

README.md

ungoogled-chromium Ti-R

I did a fork of ungoogled-chromium repository.

I didn't change it much, The old readme under this short description is still valid,

I create a branch with the version 67.0.3396.87-3 to add patch for a new logo.

New logo

To represent the "ungoogled" part inside the logo, a part of it got wash out of colors. The other part of the logo got more vivid color to show how great this version is!

I also changed the tab to rectangled corner. After the patch was made, I just saw the Chromium v69 got the same feature... rectangled corner... I thought the day of rectangle corner wil never came, but it did ;)

Anyway, the logo patch still remain with the rectangled corner.

All under the branche name "release/67.0.3396.87-3/Ti-R_v1.0"

Tag 67.0.3396.87-3_Ti-R_v1.0

You can download already build binaries for Windows on my website. http://www.ti-r.com

ungoogled-chromium

Modifications to Google Chromium for removing Google integration and enhancing privacy, control, and transparency

Motivation and Description

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. 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. Even the final build output includes some pre-built binaries. Fortunately, the source code is available for everything.

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 are minor and do not have significant impacts on the general user experience)

ungoogled-chromium should not be considered a fork of Chromium. The main reason for this is that a fork is associated with more significant deviations from the Chromium, such as branding, configuration formats, file locations, and other interface changes. ungoogled-chromium will not modify the Chromium browser outside of the project's goals.

Since these goals and requirements are not precise, unclear situations are discussed and decided on a case-by-case basis.

ungoogled-chromium is looking for contributors. See the Contributing, Reporting, Contacting section for more information.

Table of Contents

Features

A number of ungoogled-chromium's changes are subtle and evolve over time. As a result, it is best to consult the source code for complete and up-to-date information.

ungoogled-chromium selectively borrows many of its features from the following:

Most of the additional features are as follows:

  • Replace many web domains in the source code with non-existent alternatives ending in qjz9zk (known as domain substitution; see DESIGN.md)
  • Strip binaries from the source code (known as binary pruning; see DESIGN.md)
  • Disable functionality specific to Google domains (e.g. Google Host Detector, Google URL Tracker, Google Cloud Messaging, Google Hotwording, etc.)
  • Add Omnibox search provider "No Search" to allow disabling of searching
  • Disable automatic formatting of URLs in Omnibox (e.g. stripping http://, hiding certain parameters)
  • Added menu item under "More tools" to clear the HTTP authentication cache on-demand
  • Add new command-line switches and chrome://flags entries:
    • --disable-beforeunload - (Not in chrome://flags) Disables JavaScript dialog boxes triggered by beforeunload
    • --disable-search-engine-collection - Disable automatic search engine scraping from webpages.
    • --enable-stacked-tab-strip and --enable-tab-adjust-layout - These flags adjust the tab strip behavior. --enable-stacked-tab-strip is also configurable in chrome://flags Please note that they are not well tested, so proceed with caution.
    • --extension-mime-request-handling - Change how extension MIME types (CRX and user scripts) are handled. Acceptable values are download-as-regular-file or install-always. Leave unset to use normal behavior. It is also configurable under chrome://flags
    • --fingerprinting-client-rects-noise - Implements fingerprinting deception of JS APIs getClientRects() and getBoundingClientRect() by scaling their output values with a random factor in the range -5% to 5%, which are recomputed for every document instantiation.
    • --set-ipv6-probe-false - (Not in chrome://flags) Forces the result of the browser's IPv6 probing (i.e. IPv6 connectivity test) to be unsuccessful. This causes IPv4 addresses to be prioritized over IPv6 addresses. Without this flag, the probing result is set to be successful, which causes IPv6 to be used over IPv4 when possible.
  • Force all pop-ups into tabs
  • Disable Safe Browsing
  • Disable intranet redirect detector (extraneous DNS requests)
    • This breaks captive portal detection, but captive portals still work.
  • Add more URL schemes allowed for saving
  • (Iridium Browser feature change) Prevent URLs with the trk: scheme from connecting to the Internet
    • Also prevents any URLs with the top-level domain qjz9zk (as used in domain substitution) from attempting a connection.
  • (Iridium and Inox feature change) Prevent pinging of IPv6 address when detecting the availability of IPv6. See the --set-ipv6-probe-false flag above to adjust the behavior instead.
  • Support for building Linux packages for multiple distributions (work in progress)
  • Windows support
    • Does not set the Zone Identifier on downloaded files

NOTE: Although it is the top priority to eliminate bugs and privacy-invading code, there will be those that slip by due to the fast-paced growth and evolution of the Chromium project.

Supported platforms and distributions

Currently, only desktop platforms are supported. Functionality of specific desktop platforms may vary across different releases. For more details, see Statuses in the Wiki.

Other platforms are discussed and tracked in GitHub's Issue Tracker. Learn more about using the Issue Tracker under the section Contributing, Reporting, Contacting.

Download pre-built packages

Contributor binaries

IMPORTANT: These binaries are provided by anyone who are willing to build and submit them. Because these binaries are not necessarily reproducible, authenticity cannot be guaranteed.

All downloads

The release versioning scheme follows that of the tags. See the next section for more details.

Alternative installation methods

Arch Linux: Available in AUR as ungoogled-chromium

macOS cask: Available as eloston-chromium

Getting the source code

Users are encouraged to use one of the tags. The latest tag may not be the applicable for all platforms. To determine the tag to use, please see the Status page in the Wiki.

Tags are versioned in the following format: {chromium_version}-{release_revision} where

  • chromium_version is the version of Chromium used in x.x.x.x format, and
  • release_revision is a number indicating the version of ungoogled-chromium for the corresponding Chromium version.

Frequently-asked questions

See FAQ.md

Design and implementation

See DESIGN.md

Building

See BUILDING.md

Contributing, Reporting, Contacting

You may submit feedback (i.e. problems, suggestions, and questions) to the Issue Tracker.

  • The Issue Tracker the main hub for development activity; It tracks problems, suggestions, and questions. Issues marked with the help wanted tag are changes that needs discussion or assistance.

Pull requests are welcome! Here are the general guidelines:

  • Minor changes, such as bug fixes, documentation fixes, or small feature additions, will generally not need prior approval.
  • More significant changes should be discussed via an issue first.
  • When in doubt, create an issue.

There is also a Gitter chat room for those who prefer real-time discussion.

Credits

License

BSD-3-clause. See LICENSE