ungoogled-software/ungoogled-chromium

Description Add a flag that disables the functionality of Web Audio API features while allowing audio playback through / Who's implementing? I'm willing to implement this feature myself The problem The Web Audio API is a fingerprinting attack vector (ex. https://fingerprint.com/blog/audio-fingerprinting/) and can allow websites to play unwanted audio. Ungoogled-chromium already includes features to disable other annoyances and close fingerprinting attack vectors. Possible solutions The addition of a flag/setting to control the Web Audio API. I see this having three options: Default - Web Audio API works as normal Fingerprint Deception - Apply an algorithm to attempt to deceive fingerprinting algorithms - this has been done in other browsers such as Brave (https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections) Disabled - Disable the Web Audio API entirely / replace with no-op Alternatives Muting a site/disabling audio playback entirely does not disable the Web Aud

Description Add the flag "Reading Mode" back, and if possible , add "Media Router" and "Global Media Router" back too. Who's implementing? I'm willing to implement this feature myself The problem As suggested in ungoogled-software/ungoogled-chromium-windows#615, I decided to post the FR here. The flag "Reading Mode" used to be an original chromium flag but was removed in later versions as shown below (test version: https://github.com/ungoogled-software/ungoogled-chromium/releases/tag/118.0.5993.117-1): "Media Router" and "Global Media Controls" used to be original chromium flags too, but now they could still be disabled by adding " -disable-features=GlobalMediaControls,MediaSessionService,MediaRouter" in the shortcut (#3822). However, this method might be disabled in the future, so turning them to be flags would be a better choice. I would appreciate it if you were willing to consider restoring these flags. Possible solutions I'm not sure how many lines of code would be needed

Description Adding a new feature flag to enable QUIC for sites served using certificates signed by a locally trusted custom CA Who's implementing? I'm willing to implement this feature myself The problem In default Chromium, QUIC is explicitly disabled for sites served with a certificate signed with a custom CA even if it's trusted. Discussion here https://groups.google.com/a/chromium.org/g/proto-quic/c/aoyy_Y2ecrI/m/R-Mdl9noBAAJ?pli=1 Possible solutions I'd like to add a flag to enable this (disabled by default to map the default chromium behavior) Alternatives No response Additional context I've already implemented a small patch which works, but I'm wondering if this is ok for the ungoogled-chromium feature criteria before submitting the PR

Description Replace .qjz9zk "TLD" with the specification compliant .invalid TLD for domain substitution. Who's implementing? I'm willing to implement this feature myself The problem I believe it would be a technical better approach instead of using a random combination of letters and numbers as TLD to block unwanted connections, using the invalid TLD which was specifically for this use-case to always be an invalid connection. This would be more straightforward to users, who encounter a connection that was blocked using the qjz9zk TLD method. https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq#why-are-there-urls-with-the-qjz9zk-domain-in-them-why-use-domain-substitution Possible solutions Replace .qjz9zk with .invalid. https://www.rfc-editor.org/info/rfc2606/ https://en.wikipedia.org/wiki/.invalid Alternatives No response Additional context No response

Description Support Vimium like keyboard shortcuts. Who's implementing? I'm willing to implement this feature myself The problem It improves productivity reduces strain on health and improves usage for people with disabilities. Possible solutions Report upstream (i cant, because I don't have/want a Google account): https://issues.chromium.org/issues?q=keyboard%20navigation Alternatives No response Additional context No response