You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: ungoogled-chromium already incorporates the Brave canvas/audio/rects
noise features via flags inherited at build time. Patches 22-25 may
collapse to enabling and re-keying existing features — see specs.
E. Audio (Hard — port from Brave)
#
Patch
Idea source
Category
Status
26
AudioContext output noise (deterministic per seed)
Brave audio farbling (MPL-2.0)
🟠
spec
27
AnalyserNode output noise
Brave
🟠
spec
28
AudioBuffer.getChannelData noise
Brave
🟠
spec
F. Fonts (Moderate — fresh, but needs filesystem prep)
navigator.gpu.requestAdapter() consistent with WebGL vendor
WebGPU spec
🟡
spec
Build-order / dependency notes
Patches 32-35 (time/locale) depend on #32 landing the CLI plumbing first.
Patches 11-15 (screen/window) share a single CLI struct; group commit.
Patches 22-25 (canvas) may all be served by enabling and re-keying
ungoogled-chromium's existing Brave-derived features — spec out the
re-keying first before writing new canvas patches.
Patches 40-44 (TLS/HTTP) are the highest-risk; consider deferring until
the rest land and measure detection delta.
Estimated effort
Category
Patches
Senior-Chromium-engineer time
A Navigator
10
2 weeks
B Screen
5
1 week
C WebGL
6
3 weeks (incl. GPU pool research)
D Canvas (re-key existing)
4
1 week
E Audio (port Brave)
3
1 week
F Fonts
3
2 weeks
G Time/Locale
4
1 week
H Storage
2
3 days
I WebRTC
2
1 week
J TLS/HTTP
5
4 weeks (highest risk, may need libcurl-style approach)
K Headless
4
1 week
L WebGPU
1
3 days
49
~17 weeks (~4 months)
Per-Chromium-release rebase (every 4-6 weeks): ~3-5 days.