> A Chromium fork can only sever itself from Google’s control if it is not taking patches from upstream (ie, Google). I’m particularly thinking about the most consequential pieces: web APIs, not Google ad tech.
It's generally far easier to turn APIs off than add new things. Keeping a fork up to date with upstream while maintaining a list of Chromium platform additions that are disabled is exactly what we're talking about here, no?