Chrome 71 will block any and all ads on sites with "abusive experiences"
Google is promising to punish sites that offer what the company calls "abusive experiences." Chrome 71, due for release in December, will blacklist sites that are repeat offenders and suppress all advertising on those sites.
The behaviors deemed abusive cover a range of user-hostile things, such as ads that masquerade as system error messages, ads with fake close boxes that actually activate an ad when clicked, phishing, and malware. In general, if an ad is particularly misleading, destructive, or intrusive, it runs the risk of being deemed abusive.
Chrome already takes some actions against certain undesirable website behaviors; it tries to block popups, it limits autoplay of video, and it blocks certain kinds of redirection. These measures have been insufficient to prevent misleading or dangerous ads, hence Google taking further steps to banish them from the Web.
Also at The Verge, 9to5Google, Engadget, and Search Engine Journal.
Previously: Google Preparing to Filter "Unacceptable Ads" in 2018
Google Chrome to Begin Blocking "Non-Compliant Ads" on Feb. 15
(Score: 3, Interesting) by Runaway1956 on Tuesday November 06 2018, @06:00PM (8 children)
uBlock Origin, uMatrix, and half a dozen other script blockers work perfectly well. They will even block Google's own prying into your life! Add in the MVPS hosts file, http://winhelp2002.mvps.org/hosts.htm [mvps.org] and you're already miles ahead of what Google is offering with this updated browser. If your router is configurable, you can block all sorts of sites, including those Microsoft forced updates.
I use some Google services. Do I trust Google? Not only "NO", but "HELL NO!"
Chromium is built to spy on you, the user. Perhaps the spying is less obnoxious than some of what it promises to block, but they are still spying on you.
(Score: 3, Interesting) by Pino P on Tuesday November 06 2018, @06:50PM (2 children)
Using /etc/hosts as a means of content filtering is effective for some sources but not others. In particular, if the source randomizes the subdomain (such as 192bd0.badsite.example vs. a9f78a.badsite.example), the most widely supported syntax for /etc/hosts cannot cover all possibilities because it lacks wildcard support.
(Score: 0) by Anonymous Coward on Wednesday November 07 2018, @06:15AM (1 child)
This is true of any blacklist.
(Score: 2) by Pino P on Wednesday November 07 2018, @02:22PM
The point that one notorious Anonymous Coward on the green site appears not to get is that this is less true of a wildcard blacklist than a single-hostname blacklist.
(Score: 4, Informative) by WizardFusion on Tuesday November 06 2018, @06:59PM
Use https://pi-hole.net/ [pi-hole.net], a much better solution.
(Score: 2) by edIII on Tuesday November 06 2018, @07:35PM (3 children)
Do you mean Chrome, or Chromium? There isn't much choice these days I'm afraid. Firefox still runs like shit, and there is no IE on Ubuntu :)
I've tried other browsers but they are not as good.
So what information is Chromium leaking? I thought that was the open source version that I could compile if I wanted (which I may try here), and that people are generally looking at it.
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 0) by Anonymous Coward on Wednesday November 07 2018, @06:18AM (2 children)
This covers some of the problems https://github.com/Eloston/ungoogled-chromium [github.com]
(Score: 2) by Wootery on Wednesday November 07 2018, @02:29PM (1 child)
There's also Vivaldi, if you don't mind that they aren't FOSS.
(Score: 2) by toddestan on Friday November 09 2018, @03:26AM
There's also completely open source wrappers around the Blink engine such as Falkon (formerly Qupzilla).
Though honestly Firefox has improved quite a bit in comparison to Chrome, though I prefer Palemoon.