HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gcarq
inox-patchset
Shell2015–2018
gcarq / inox-patchset · Archived

inox-patchset

Inox patchset tries to provide a minimal Chromium based browser with focus on privacy by disabling data transmission to Google.

10Distinct people
10Mentions
0Explicit recommenders
388GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Inox patchset tries to provide a minimal Chromium based browser with focus on privacy by disabling data transmission to Google.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2015-12-06 15:46:16 UTC to 2018-12-06 18:16:13 UTC.

012342015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC404

What Hacker News says

10 sources
> You can always use Chromium (premade build or make your own build), get the benefits of Chrome's security without the potential tracking. My understanding is that statement is false; let's be careful not to mislead people about these issues. And in that spirit, I should make clear that my understanding is based only on the following, not on direct knowledge: * The ungoogled-chromium project, which aims to remove from Chromium the privacy threats from Google: https://github.com/Eloston/ungoogled-chromium 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-bui
Read the rest
lt binaries provided by Google. Even the final build output includes some pre-built binaries. * There's also the Inox patchset, with similar aims: https://github.com/gcarq/inox-patchset Inox patchset is applied on the chromium source code and tries to prevent data transmission to Google to get a minimal Chromium based browser * And finally, Iridium, a browser based on Chromium: https://iridiumbrowser.de/ Chromium (which Iridium is based on) is a very secure browser, yes. But it does call home to Google and we did even more to enhance security to the maximum extent possible.
In Firefox does not have a well-designed privsep model
- Delete all Google Accounts - Flash AOSP (Compiling it from source rather than a pre-compiled rom is even better) - Install microG, a drop in FOSS replacement for Google Play Services | https://microg.org/ - Install F-Droid | https://f-droid.org/ - Install Yalp Store, an app for downloading apks from Google Play Store via F-Droid | https://f-droid.org/repository/browse/?fdfilter=yalp&fdid=co... - Build CAF, Chromium for Snap Dragon | https://source.codeaurora.org/quic/chrome4sdp/ and tweak as you like. I add DuckDuckGo as my primary search and also use a majority of the patches from the inox-patchset | https://github.com/gcarq/inox-patchset --- With microG and Yalp you'll be able to cover 95% of your proprietary app needs. For example, I use it to occasionally install Slack when I work remote. But remember to always use the unstable vers
Read the rest
ion of microG so the latest apps won't complain about your Google Play Services being out of date.
In Ask HN: How to increase privacy on Google phones/devices?
There's Chromium Inox[0] which is just a patchset on top of the Chromium build to remove much of the mothership home-calling. Inox seems to be much closer to Chromium than many of the other Chrome-privacy spinoffs. Contrary to popular belief, Chromium still has a lot of Google in it. I always feel like artificially patching a project that doesn't care about your concerns natively to be plugging holes in a sponge boat, but I realize sometimes you need to use that boat because reasons. I installed it from the AUR and it seems to work pretty well for the testing I do in it anyway. I don't daily driver it or Chrome. [0] https://github.com/gcarq/inox-patchset
In Google will use Chrome browsing data for ad tailoring

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.