Hacker News Reader

Comment by Kristine1975 | Hacker News Reader

Kristine1975

This opt-out works for me (add to hosts file):

  127.0.0.1 www.google-analytics.com 
  127.0.0.1 google-analytics.com 
  127.0.0.1 ssl.google-analytics.com

View on HN

What about the doubleclick domains and adwords domains which feed the same data into the same system too? And what about when they launch a new domain? (Would be difficult to keep up with those changes)

Use own root and cache DNS instead of HOSTS. Then use wildcards, e.g.,

  *.doubleclick.net

Tool to automate that: https://github.com/jakeogh/dnsmasq-blacklist

The question is: what is listening on 127.0.0.1?

For example, do you have an httpd listening on 127.0.0.1? Do you bind any other daemons to 127.0.0.1 or the broadcast address?

If you operate your own root you can reassign the authoritative nameservers for doubleclick.net to nameservers you control. You may or may not choose to return "A" records.

Hopefully nothing is on 127.0.0.1:80/443, that way webkit gets a RST back, which I assume is faster (and less error prone) than serving a dummy page. I'll add a note to the README.

Edit: Added a --dest-ip option

"...serving a dummy page."

It could also be less than a page. It could be a dummy resource. For example, in the case of an ad server and a smartphone app that has some screen space reserved for ads. You might want your own resource to appear in that space instead.

Another example is reverse engineering API's and protocols for popular web services, social media, storage, etc. In that case you might want a "dummy server" that serves certain responses.

Interesting. Does --dest-ip[1] solve this?

[1] https://github.com/jakeogh/dnsmasq-blacklist/commit/554e20a3...

I just use NoScript.

Be careful because the Google Analytics code (newest version includes a noscript section that loads an iframe within it) - No script will not block that.

So, uBlock then. Set 3rd-party, 3rd-party frames, and 3rd-party images to default-deny. As above, you can effectively block GA even if the noscript loads an iframe if you can block that iframe.

Or, if you are a serious, no-nonsense paranoiac uBlock even allows you to block 1st-party and inline scripts.

The world is your oyster. Block with reckless abandon! Watch the world burn! (mostly kidding with that last one)

Yes, UBO+NoScript has made browsing much more pleasant.

> Be careful because the Google Analytics code (newest version includes a noscript section that loads an iframe within it)

No it doesn't[1]? What are you referring to?

[1] https://developers.google.com/analytics/devguides/collection...

The tag manager does. The code you are linking to is a developer reference for the raw tracking code.

The tag manager has a "noscript" tag that points to an iframe with the domain googletagmanager.com

What about RequestPolicy?

Reply on news.ycombinator.com