No, Google no controls Chromium, despite Chromium as is use a lot or Google APIs. But Chromium is FOSS and because of this a lot of Chromiums are “degoogled” or parcial “degoogled” leaving some APIs as Option in the settings (Vivaldi permits even to quit the API for the Chrome Store in the settings page, if you don’t want extension from there). The difference in Chrome itself, EDGE, Opera and others, is that they all use a lot of own tracking APIs above the default from Chromium.
Sure it’s FOSS, but who’s actually working on the codebase? That’s right, google employees. Good luck submitting patch if your patch runs counter to google’s interests.
Yeah? Manifest V3 wants to have a word with you and your completely independent de-googled Browser.
Some might be able to put in the work to delay the rollout but at one point anything not supporting V3 will just break compability, completely unintentional obviously.
No, Google no controls Chromium, despite Chromium as is use a lot or Google APIs. But Chromium is FOSS and because of this a lot of Chromiums are “degoogled” or parcial “degoogled” leaving some APIs as Option in the settings (Vivaldi permits even to quit the API for the Chrome Store in the settings page, if you don’t want extension from there). The difference in Chrome itself, EDGE, Opera and others, is that they all use a lot of own tracking APIs above the default from Chromium.
Sure it’s FOSS, but who’s actually working on the codebase? That’s right, google employees. Good luck submitting patch if your patch runs counter to google’s interests.
Yeah? Manifest V3 wants to have a word with you and your completely independent de-googled Browser. Some might be able to put in the work to delay the rollout but at one point anything not supporting V3 will just break compability, completely unintentional obviously.