[AlexanderTheGr8]

Not trying to throw ML at the wall, but could it be used for this problem (considering all other options seem to be failing)?

As far as I understand, after MV3, ad blockers won't be able to use a long list of ads to remove them.

How about using a simple ML algorithm to detect whether the request is a genuine one or an advertisement? I am sure that getting training data wouldn't be too hard (all the ad lists that will get useless after MV3 are good data).

I don't make chrome extensions so I don't completely know how MV3 will cripple ad blockers.

Any feedback would be appreciated!

[jimmydorry]

The point of the change is to go from allowing extensions unfettered access to read, rewrite and exfiltrate everything you request, to forcing them to declare upfront what they will block.

Sure, there are still going to be some work arounds that still allow extensions to read and change what a user sees, but anyone looking at this honestly can see what the intention is.

Throwing ML at this problem doesn't make sense at all as reading and then rewriting requests is exactly what Google doesn't want extensions doing anymore.