Where to track ungoogled-chromium relevant privacy patches & improvements?

[dm17]

This article inspired me to ask this question today: "Chrome exempts Google sites from user site data settings" https://lapcatsoftware.com/articles/chrome-google.html

Where are new new privacy invading anti-features from Google tracked? I mean: are they all defaultly patched, or are ungoogled-chromium users expected to look for patches to stuff like URL hiding, the upcoming manifest (v3), and AMP on top of ungoogled-chromium?

Thanks a lot to all relevant devs!

[omentic]

See https://github.com/Eloston/ungoogled-chromium#feature-overview.

To directly answer your questions: you can look in the patches folder, they're all applied by default (although it does depend on your build), removing http:// hiding is one of those patches, Manifest v3 has been / is discussed in #662 , and AMP is out of scope.

[wchen342]

Well this leads to a broader problem that the project needs some kind of resource management to track core (google-related) issues, maybe also some auditing?

[dm17]

Well this leads to a broader problem that the project needs some kind of resource management to track core (google-related) issues, maybe also some auditing?

The only thing I can think of is using CI.

[omentic]

@wchen342 Do you mean other than Github Issues? I'm not a contributor to this project, but that seems to be where all relevant discussion / tracking has been happening.

[Eloston]

@wchen342 You have a point, the issue tracker isn't really organized right now. We need to rethink the labeling scheme for issues, and consider how GitHub Discussions should be involved here. The current system (using Issues with minimal labeling) isn't scaling well to handle the project's growth.