3 ms·
I don't even think you can say adblockers are a "power user" feature. The web is so bloated and bad that it's virtually unusable without it. I hope this gets f
by hbn 4y ago
I don't even think you can say adblockers are a "power user" feature. The web is so bloated and bad that it's virtually unusable without it.
I hope this gets found as the anti-competitive move that it is. They're taking advantage of their near-monopoly that they have in the browser space to force people to view more of their own ads. It's disgusting.
- Raed667 4y agoAdblocking is the tip of the iceburg. Proxying, dev-tools that manipulate CORS, rule-based cosmetic filters etc... will also be impacted. The other huge change that most people don't know about, is the move from a persistent background.js script to a sevice-worker will just make a number of use-cases impossible or very hacky
- aeharding 4y ago> the move from a persistent background.js script to a sevice-worker will just make a number of use-cases impossible or very hacky Yep. Chrome is even crippling some of their own APIs, like chrome.tabCapture (not available in service workers, and in mv3 will be "foreground only") AKA, if you want to use chrome.tabCapture in mv3, you have to run it in a tab. And because that tab can be closed at any time, you need to serialize megabytes of data to the chrome.storage api every few seconds.
- msallese31 4y agoDoes running it in a content script even work? I've only been able to run tabCapture in the popup. I don't see how any screen recording extensions can work in MV3