<story><title>Mozilla’s Manifest v3 FAQ</title><url>https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest-v3-faq/</url></story><parent_chain></parent_chain><comment><author>WhatIsDukkha</author><text>The tone of this post concerns me.&lt;p&gt;What comes across is that Google is not collaborating with Mozilla over the Manifest v3 changes.&lt;p&gt;Instead of using and appreciating the engaged Firefox developer ecosystem we have PM conference rooms in Google mandating huge changes based on... well they&amp;#x27;ve been shady so far about their choices on Manifest v3.&lt;p&gt;The other thing that keeps bugging me about this is -&lt;p&gt;We need a tiered App store for browsers. Part of the lockdown Google wants to do isn&amp;#x27;t wrong but its driven by having WAY too many bad actors and shoddy developers in their Chrome store.&lt;p&gt;If you have an opensource web extension, a reasonable community and with reproducible builds? You can use more powerful API versions.&lt;p&gt;If you are jrando bizplan #2000283 you get the kinda trusted tier.&lt;p&gt;Frankly if Debian had a web browser extension &amp;quot;store&amp;quot; with 20 things in it, I&amp;#x27;d use that exclusively and turn off both the Chrome and the Firefox store 100%.</text></comment>
<story><title>Mozilla’s Manifest v3 FAQ</title><url>https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest-v3-faq/</url></story><parent_chain></parent_chain><comment><author>danShumway</author><text>&amp;gt; In the absence of a true standard for browser extensions, maintaining compatibility with Chrome is important for Firefox developers and users.&lt;p&gt;About as close as Mozilla can come to outright saying, &amp;quot;Chrome is big enough and we&amp;#x27;re small enough that what they do _is_ the standard.&amp;quot;&lt;p&gt;Still, it&amp;#x27;s encouraging to see that they&amp;#x27;re not removing the blocking API for now. I kind of hope this does push a few adblocker extensions to abandon Chrome.</text></comment>