Google uses EasyList and EasyPrivacy which includes AdSense, DoubleClick, Analytics, and other Google properties. Read the article.
A comparable situation would be Windows 10 ignoring users' manually edited HOSTS file that attempts to block telemetry.[1] Microsoft has hardcoded hostname-to-ip resolution inside the networking stack (inside dnsapi.dll).
If Google decides that Chrome will ignore some entries in EasyList, it means EasyList is more of a "suggestions" filter rather than a "user's final authority" filter.
[1] https://www.petri.com/windows-10-ignoring-hosts-file-specifi...
It's funny how Microsoft under Satya Nadella is heralded for opening up (embracing[0] open source, open standards, recognizing other platforms).
[0] I only noticed the irony a few seconds after writing that.
The article's sentence: "Google appears to be shipping the entirety of EasyList and EasyPrivacy; which includes blocking rules for Google’s own AdSense and DoubleClick advertisement platforms as well as Google Analytics,"
... is only talking about the existence of AdSense on EasyList -- because the entirety of EasyList entries is shipped. It does not talk about (or even speculate) whether Chrome will have a programming code that implements a whitelist to ignore certain entries.
Those are 2 different concepts.
>The Better Ads Standards are a set of rules, one set for desktop and one for mobile, that define unacceptably intrusive, distracting, and annoying advertisement formats.
If so, "Better Ad Standards" is orthogonal to "AdSense standards".
Or put another way, "unacceptably intrusive, distracting, and annoying" is orthogonal to blocking "AdSense" url _domains_. E.g. See layout rules from AdSense guidelines.[2]
Why are we parsing the text differently? Are we talking about 2 different abstraction levels? I'm talking about EasyList as a network traffic filter. Maybe others are talking about EasyList as a rule source for _rendering_ DOM elements. (E.g. if AdSense is rendered in an intrusive popup overlay which already violates Google's rules and wil get AdSense accounts banned even before "Better Ads Standards" was adopted.) These are 2 different concepts.
Let's not over-read things in the article that are not actually there.
It could not be more clear all ads will be removed from failing sites.
https://developers.google.com/web/updates/2017/12/better-ads
Again, I wasn't talking about "failing _websites_". I was talking about ad serving _domains_.
You've lost track of what the conversation was about and the substance of what I was responding to. Please re-read the previous post to reset.[1]
That post by d2wa was claiming a direct cause-&-effect blocking based purely on entries in EasyList.
I replied that the article makes no such irrefutable claim and that he was over-reading something that wasn't there.
You, on the other hand, are talking about "Better Ad Standards"[2] which is orthogonal to my reply to d2wa. Your repeated citation of it actually muddles the topic because the Google's longstanding approved rules for the correct layout of AdSense already adheres to "Better Ad Standards".
To restate the different conversations in pseudo-code...
Argument by d2wa:
if (EasyList_entry_exists("AdSense"))
block();
BetterAdStandardsViolation = popup || autoplaysound || prestitialcountdown || largesticky;
if (BetterAdStandardsViolation)
block();
if (BetterAdStandardsViolation) {
if (EasyList_entry_exists)
block(); // this line of code unreachable by correct use of AdSense
}
EasyList is not the final authority on blocking AdSense. Since Google's existing guidelines for proper AdSense layout already complies with "Coalition for Better Ads", the existence of AdSense in EasyList is not relevant because the EasyList filter is selectively applied to failing websites. In other words, Chrome's ad blocker will not block AdSense the same way as uBlock.
[1] https://news.ycombinator.com/item?id=16297718
So are we in agreement then? Google’s ad sense ads will be removed from sites that violate the better ad standard guidelines per google’s official documentation on this feature.
If so, the question here that you originally posed would be answered in the negative:
“I read the article but it doesn't clarify whether or not Google will hardcode a "whitelist" that will ignore EasyList entries for AdSense, DoubleClick, GoogleAnalytics, etc.”
No. the answer is "positive" in the context of my reply to d2wa of how EasyList is not obeyed. The "whitelist" is achieved by correct use of AdSense. (See pseudo-code example #3 of how EasyList filter code is never reached for AdSense.) It does not work like uBlock.