Sundar Pichai, vice president of Chrome, speaks at Google's annual developer conference / Getty Images Google is working to make the...
Sundar Pichai, vice president of Chrome, speaks at Google's annual developer conference / Getty Images |
Google's Chrome browser will block battery-draining, data-guzzling ads, and this will see Cryptocurrency Ads being targeted.
“These ads (such as those that mine cryptocurrency, are poorly programmed, or are unoptimized for network usage) can drain battery life, saturate already strained networks, and cost money,” Vale wrote in a Thursday blog post. In response, Google will limit the system resources an online ad can use before you click on it. “When an ad reaches its limit, the ad's frame will navigate to an error page, informing the user that the ad has used too many resources,” Vale added.
As the example below shows, the intrusive ad will come up as a gray blank space, rendering it useless. According to Vale, Google plans on targeting the most egregious ads that use more CPU or network bandwidth than 99.9 percent of ads that tap the same system resources. Specifically, the company will block ads that meet any of the following criteria:
-
Uses the main CPU for more than 60 seconds in total.
-
Uses the main CPU for more than 15 seconds in any 30-second window.
-
Uses more than 4 megabytes of network bandwidth.
You'll then be brought to a screen, where you can turn it on. Shady ad companies and in-browser cryptocurrency mining providers will probably hate the move, but the upcoming change is part of the company’s ongoing effort to prevent users from flocking to more powerful ad-blocking software, which risks undermining Google’s main business of serving ad space.
“Our intent with this extended rollout is to give appropriate time for ad creators and tool providers to prepare and incorporate these thresholds into their workflows,” Vale said. “To help advertisers understand the impact of this intervention on their ads, they can access reports to learn which ads Chrome unloaded.”This article originally published at PCMag here.