I find the "switch to Safari" talk amusing because the adblockers available for Safari are functionally equivalent to the MV3 API that everyone's complaining ab

I find the "switch to Safari" talk amusing because the adblockers available for Safari are functionally equivalent to the MV3 API that everyone's complaining about. The problem with the "static list of content to block" approach that Safari and MV3 use is that you can't trick the site into thinking that ads have been loaded when they haven't, like MV2 allows via Javascript injection. The effect of this is that you'll run into a lot of "disable your ad blocker to continue" pop-ups when using an adblocker with Safari, while you won't see them at all when using an adblocker with Firefox.