Basicotter1919

Almost as soon as a design draft for Manifest V3 was made public, on November 9th 2018,  developers disapproved of the changes proposed by it, including the developers of privacy and security-focused tools such as NoScript, AdGuard, uMatrix, and uBlock Origin.<ref>{{Cite web |date=2018-10-18 |title=Extensions: Implement Manifest V3 |url=https://issues.chromium.org/issues/40598795 |url-status=live |website=issues.chromium.org}}</ref> On January 22, 2019, in response to the design draft, the developer for uBlock Origin and uMatrix would go on to write, "if this [...] API ends up being the only way content blockers can accomplish their duty, this essentially means that content blockers I have maintained for years, uBlock Origin ("uBO") and uMatrix, can no longer exist." And also, "[...] deprecating the blocking ability of the [...] API will essentially decrease the level of user agency in Chromium, to the benefit of web sites which obviously would be happy to have the last word in what resources their page can fetch/execute/render."<ref>{{Cite web |date=2019-01-22 |title=Extensions: Implement Manifest V3, comment #24 |url=https://issues.chromium.org/issues/40598795#comment24 |website=issues.chromium.org}}</ref> A developer for AdGuard would second his points. In response, a Chromium developer did not immediately answer these points, but instead directed the discussion to take place over email rather than the bug tracker.<ref>{{Cite web |date=2019-01-22 |title=Extensions: Implement Manifest V3, comment #34 |url=https://issues.chromium.org/issues/40598795#comment24 |url-status=live |website=issues.chromium.org}}</ref>