That needs minimal effort compared to building a browser, because it doesn't involve doing any of the hard work, but just removing code that serves to line the pockets of those doing most of the work at the expense of the user.
That needs minimal effort compared to building a browser, because it doesn't involve doing any of the hard work, but just removing code that serves to line the pockets of those doing most of the work at the expense of the user.
Also the mission you are describing sounds like something that you might expect from a Chromium browser that has to regularly revert Google-driven changes. At Mozilla, they already own the browser and they could account for this in their ground-level philosophy.
By whom and on what basis? Those are non-optional questions that should have strong answers as preconditions to you posting about it, if the objective is to offer something more than simple bullshitting (in the Harvey Frankfurt sense of indifference to truth).
This also doesn't answer like 90% of my concerns from my previous comments. Who has ever intentionally had a software development approach of having one team develop features and another person revert those features, working in tandem? And why would they need donations that are 0.20% of what they already get in revenue to finance it? I feel like you're just improv riffing here.