Conversation

Replying to
lmao remember when Google used Chrome to do exactly the same thing several times for exactly the same reason and using exactly the same rationale
1
4
Replying to and
"we're saving you from all the bad advertisers out there who are completely unlike us in respect for users (and also coincidentally do not provide us with huge stacks of cash)"
2
2
Replying to and
They didn't really do anything with that because they were scared of anti-trust action if they started blocking ads on sites with ads hurting usability. They added a content filtering engine to Chromium and distributed EasyList in an optimized form but.. it's not really used.
2
Chromium still has this content filtering engine, tooling to generate optimized content filtering lists for it from EasyList style filters using the same syntax and they ship a version of EasyList as a component called Subresource Filter Rules (look at chrome://components).
1
Safe Browsing is used to determine if it should be used. It's possible they enable it on sites that are considered malicious by Safe Browsing. I haven't heard of a single case where they deployed this based on the intrusive ads policy they were supposedly going to be enforcing.
Replying to and
They likely use it for sites blocked by Safe Browsing for distributing malware, etc. but I haven't seen it get used in any case based on the intrusive ads policy they proposed and were supposedly going to be enforcing. It's a punishment on top of Safe Browsing warnings AFAICT.
1
Show replies