Google will turn on native ad-blocking in Chrome on February 15

Re:Google will turn on native ad-blocking in Chrome on Febru... by Fnoord on Wednesday December 20, 2017 @09:17AM (#15969634)

Problem isn't browser on Android. You can install another like many others already said (I use Firefox + uBlock). The problem is that apps use Webview to embed. So you're going to need to use another option to block ads on Android in general:

1) Use DNS66 as another user said. Doesn't require root. (Does make a local VPN, so removes option to use a VPN.)

2) Use Pi-Hole on a Pi at home and make a VPN to it. Bonus: you get access to your home network (if you config it as such) and are secure over open WiFi and hostile 4G. Doesn't require root.

3) You can root your phone and use /etc/hosts or IPT

4) Firefox 58 will allow you to run tabs as "apps" which are pinned in the OS. If that takes off, that's going to result in a massive dent in paid apps from Google Play as well as ad revenue from Android.

As for this action by Google, its a charming move. Remember that time when Google was just new, and was only text ads on Google search engine?

[ Parent | on HN ]

Re:Google will turn on native ad-blocking in Chrome on Febru... by Spivak on Wednesday December 20, 2017 @02:51PM (#15973105)

Some apps might use a WebView but any app that's using custom tabs ('Chrome tabs') can take advantage of the browser ad blocking. For Firefox all you have to do is turn it on in Firefox and make it your default browser.

You can already do 4 with sites that support being a PWAs and it's pretty good.

[ Parent | on HN ]

Re:Google will turn on native ad-blocking in Chrome on Febru... by Fnoord on Wednesday December 20, 2017 @03:00PM (#15973191)

AFAIK most apps use WebView. I use Firefox as default browser (even disabled Chrome, not using it), and still see ads (that is w/o any of the other methods mentioned).

PWA was part of Firefox 58 AFAIK, so you either need Firefox Beta or wait till January.

[ Parent | on HN ]