It seems we agree that in the long run, it's unsustainable. My point is more modest: that in the specific topic of this post, using response time against the blockers, Firefox is also vulnerable.
The mechanism is actually very simple if the content is served using JavaScript, as is the case with videos: make the code that shows the ads create some token and then the media player will check if it's present, refusing to play otherwise.
You can circumvent it with code, but new code triggers new review and, when it's approved, the token is changed and back to square one. In the case of Firefox it might be faster, but I don't think extension maintainers and reviewers can be 24x7 available to play that cat & mouse game.
In Firefox you need to sign extensions to install them or go through the debug menu. Both methods are not easy for the regular user. At the end of the day, either blocking turns to be only for power users/programmers, or a new trust model for browsers is adopted.
Chromium and Firefox are both open source but how many % of their users have actually compiled them from sources? I haven't. Last time I checked, Chromium recommended a minimum 0.5 TB free space. And Firefox now requires two programming languages.
I feel bad for the normies who can't or won't go looking for ways to stay safe online.
I used to compile my own Firefox because I'm picky, but yeah, not everyone has time and patience for a 30-45 minute compile on 12 year old hardware. The RAM requirements for both Firefox and Chrome are ridiculous.
It wasn't this bad before we wanted to cram everything into JS and the DOM.
The mechanism is actually very simple if the content is served using JavaScript, as is the case with videos: make the code that shows the ads create some token and then the media player will check if it's present, refusing to play otherwise.
You can circumvent it with code, but new code triggers new review and, when it's approved, the token is changed and back to square one. In the case of Firefox it might be faster, but I don't think extension maintainers and reviewers can be 24x7 available to play that cat & mouse game.
In Firefox you need to sign extensions to install them or go through the debug menu. Both methods are not easy for the regular user. At the end of the day, either blocking turns to be only for power users/programmers, or a new trust model for browsers is adopted.
Chromium and Firefox are both open source but how many % of their users have actually compiled them from sources? I haven't. Last time I checked, Chromium recommended a minimum 0.5 TB free space. And Firefox now requires two programming languages.