<story><title>Manifest V3, webRequest, and ad blockers</title><url>https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/</url></story><parent_chain><item><author>londons_explore</author><text>It&amp;#x27;s not really a wake up call - at any time they could fork and go their own way.&lt;p&gt;Just right now, they prefer to not have to pay for 1000+ engineers to work on the codebase to keep up with the pace that Google manages.</text></item><item><author>worble</author><text>&amp;gt;As Vivaldi is built on the Chromium code, how we tackle the API change depends on how Google implements the restriction. The assurance is, whatever restrictions Google adds, in the end, we’ll look into removing them.&lt;p&gt;Is this not a serious wake up call for all these companies relying on Chromium? You are staking so much of your business on a giant conglomerate that does not care about you or your users, whose only aim to sweep up as much data from the web as possible to feed their ad machine.</text></item></parent_chain><comment><author>kevincox</author><text>I&amp;#x27;m not sure a lot of these browsers have the resources to fork Chromium and stay &amp;quot;profitable&amp;quot; or whatever their goal is. Microsoft probably could but they gave up on Edge when it was pretty feature complete so I&amp;#x27;m guessing that they would really prefer not to maintain a browser by themselves. I&amp;#x27;d bet that most of the other Chromium-based browsers would not be capable of financially maintaining a serious fork where some fundamental internal APIs have been changed.</text></comment>
<story><title>Manifest V3, webRequest, and ad blockers</title><url>https://vivaldi.com/blog/manifest-v3-webrequest-and-ad-blockers/</url></story><parent_chain><item><author>londons_explore</author><text>It&amp;#x27;s not really a wake up call - at any time they could fork and go their own way.&lt;p&gt;Just right now, they prefer to not have to pay for 1000+ engineers to work on the codebase to keep up with the pace that Google manages.</text></item><item><author>worble</author><text>&amp;gt;As Vivaldi is built on the Chromium code, how we tackle the API change depends on how Google implements the restriction. The assurance is, whatever restrictions Google adds, in the end, we’ll look into removing them.&lt;p&gt;Is this not a serious wake up call for all these companies relying on Chromium? You are staking so much of your business on a giant conglomerate that does not care about you or your users, whose only aim to sweep up as much data from the web as possible to feed their ad machine.</text></item></parent_chain><comment><author>mort96</author><text>I don&amp;#x27;t think it&amp;#x27;s a preference thing. I don&amp;#x27;t think Vivaldi, or Brave, or any other company whose main product is a browser, can have the income to pay 1000+ engineers to work on the codebase to keep up with the pace of Google.&lt;p&gt;Maybe it should at the very least be a wake up call to companies which can&amp;#x27;t afford the engineer-hours it takes to maintain a Chromium fork.</text></comment>