The latest ungoogled Chromium update maintains its core mission of stripping Google web service dependencies while keeping the default browsing experience intact. A fail-safe domain substitution method blocks internal requests by replacing target domains with non-existent addresses ending in qjz9zk. Privacy features like disabling Safe Browsing and blocking tracking schemes require manual configuration, placing control squarely in the user's hands rather than automating decisions. Although this build borrows security patches from projects like Iridium and Bromite, users must accept reduced convenience for public Wi-Fi captive portals to achieve that level of isolation.

Ungoogled Chromium 146.0.7680.177-1 release strips google services and enhances control for privacy focused browsers

The latest update to ungoogled chromium arrives with a focus on removing background requests to web services. Users installing this version can expect fewer hidden connections and more manual control over browser behavior. This release keeps the default Chromium experience while aggressively cutting ties with Google infrastructure.

Why ungoogled chromium remains a viable alternative for desktop browsers

Most standard browsers treat user data as a feature rather than a bug, but this project takes a different approach. The goal here is to strip binaries from the source code and replace them with user-provided alternatives when possible. This means the browser does not rely on pre-made Google binaries that might send telemetry back home in the background. Network monitoring tools show traffic going nowhere when the qjz9zk domains are active, which proves the domain substitution trick works as intended. It is a fail-safe measure for cases where Google changes or introduces new components that patches do not disable automatically.

The technical implementation involves replacing many Google web domains in the source code with non-existent alternatives ending in qjz9zk. The browser then blocks its own requests with such domains so no connections are attempted at all. This breaks captive portal detection but ensures that intranet redirect detectors do not make extraneous DNS requests. Users who rely on public Wi-Fi might find this annoying since they often need to log into a portal page, yet the trade-off favors privacy over convenience. The project also prevents URLs with the trk: scheme from connecting to the Internet which stops tracking links embedded in web pages from working.

Manual activation requirements can slow down power users

Almost all of these features must be manually activated or enabled through configuration flags and patches. This is a double-edged sword because it requires knowledge that typical consumers do not possess. The search engine editor adds an Suggestions URL text field for customizing search engine suggestions which helps some but confuses others. There is also an Omnibox search provider labeled No Search to allow disabling of searching entirely without removing the address bar functionality. This level of granularity suggests the developers assume users will tinker with chrome flags regularly rather than just clicking icons and tabs.

The update borrows features from projects like Iridium Browser and Bromite which shows a collaborative effort to improve security. Windows users specifically benefit from not setting the Zone Identifier on downloaded files which reduces friction when opening attachments. It is worth noting that disabling Safe Browsing requires consulting the FAQ for rationale since it leaves users exposed to malicious sites by default. The project remains a lightweight approach to removing Google web service dependency without adding bloat or custom visions of what a browser should be.

Release Ungoogled Chromium 146.0.7680.177-1

Google Chromium, sans integration with Google. Contribute to ungoogled-software/ungoogled-chromium development by creating an account on GitHub.

Release 146.0.7680.177-1 · ungoogled-software/ungoogled-chromium