4 ms·
Just fine tuning how slowly to boil the frogs. At some point, they will pull the trigger. My hypothesis is that the various entities that want to work around
by tyingq 4y ago
Just fine tuning how slowly to boil the frogs. At some point, they will pull the trigger. My hypothesis is that the various entities that want to work around ad-blockers hold back for now, because they don't want to push people from the more basic blockers to the more advanced ones. Once this is in place, pretty much all adblockers of note are dns based, or semi-static list based...."basic". I wonder if there's a renewed push fighting ad blockers then.
- tjpnz 4y agoI don't understand this mentality. What do ad-tech companies like Google gain from showing an ad to an unwilling participant? Click through rates are going to crater and people are just going to stop using Chrome.
- deleted 4y ago[deleted]
- tyingq 4y agoI thought similarly about AMP. They continued the forced march, and well...
- colordrops 4y agoTheir goal is probably to slowly ween a tiny group of power users onto other browsers that allow ad blocking while acclimating everyone else to the full ad experience.
- bornfreddy 4y agoOr working on pressuring Firefox to implement MV3.
- johnny22 4y agofirefox already implements mv3 as much as they can, but without removing what mv2 offered don't they?
- cpeterso 4y agoThat’s correct. Starting in version 109 earlier this year, Firefox supports many MV3 APIs without removing or deprecating MV2 APIs. To ease the transition to MV3 for extension developers, Firefox extensions can use both MV2 and MV3 APIs. https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signing-available-november-21-on-firefox-nightly/ https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signi...
- flangola7 4y agoWhy would Firefox need to implement any of this? It's their own browser running their own engine. Why would they need to implement Chrome anything?