Gregory's Server@duco @obsolescentsapien @nixCraft I might be wrong, but it sounds like they are removing it from the browser, not the repo. If they change chromium, the change can always be reverted because it is open source. If they change the repo, they can always change the chromium to use another source for the plug-in.
@penguin_brian @duco @obsolescentsapien @nixCraft The problem with that is making a fork of a project as huge as a browser isn't realistic for small independent teams in the long term, at least not when you're making drastic changes that conflict with downstream updates. Google is still the majority code contributor to Chromium, a small team can't just take over the whole project, nor can they fight with Google's downstream updates indefinitely.