4 ms·

I find it ironic that this article includes the following trackers: - segmentio - intercomio - google analytics - doubleclick.net - facebook - mixpanel

by navs 10y ago

mirimir 10y ago
Privacy Badger detected 0 potential trackers on this page. These sliders let you control how Privacy Badger handles each one. You shouldn't need to adjust them unless something is broken. The domains below don't appear to be tracking you scout-cdn.s3.amazonaws.com cdn.embedly.com fonts.googleapis.com www.google.com fonts.gstatic.com
- ENTP 10y ago
  I can confirm navs is correct. Brave Browser indicates blocking of 9 trackers: https://googleads.g.doubleclick.net/pagead/id https://static.doubleclick.net/instream/ad_status.js https://api.segment.io/v1/p https://www.google-analytics.com/analytics.js https://widget.intercom.io/widget/ https://api.mixpanel.com/decide/ https://api.mixpanel.com/track/ https://api.segment.io/v1/t https://api.mixpanel.com/track/
  - mirimir 10y ago
    OK, so why the difference? I'm using Firefox 51.0.1 with Privacy Badger 2017.1.26, NoScript 2.9.5.3 and Adblock Plus 2.8.2. Edit: OK, so I had doubleclick.net, facebook.com, google-analytics.com and mxpnl.com untrusted in NoScript. After trusting them all, Privacy Badger still reports no tracking, but lists these trackers: cdn.embedly.com connect.facebook.net www.google-analytics.com fonts.googleapis.com www.google.com Strange. So is Privacy Badger failing to detect tracking?
    - bamboozled 10y ago
      I'm going to take a wild guess here, It's probably NoScript preventing the tracking code form being loaded before ABP can perform detections?
      - mirimir 10y ago
        Well, I did trust/allow domains in NoScript. But I gather that NoScript does other stuff by default. And there's also the fact that I'm blocking WebRTC. Mostly I was just worried that Privacy Badger was failing.
    - navs 10y ago
      Not entirely sure. Could be a side effect of the combination of extensions. On iOS I tend to simply disable javascript. Blocks much of what needs blocking.

I find it ironic that this article includes the following trackers: - segmentio - intercomio - google analytics - doubleclick.net - facebook - mixpanel

by navs 10y ago

I find it ironic that this article includes the following trackers: - segmentio - intercomio - google analytics - doubleclick.net - facebook - mixpanel

mirimir 10y ago

Privacy Badger detected 0 potential trackers on this page. These sliders let you control how Privacy Badger handles each one. You shouldn't need to adjust them unless something is broken. The domains below don't appear to be tracking you scout-cdn.s3.amazonaws.com cdn.embedly.com fonts.googleapis.com www.google.com fonts.gstatic.com

ENTP 10y ago
I can confirm navs is correct. Brave Browser indicates blocking of 9 trackers: https://googleads.g.doubleclick.net/pagead/id https://static.doubleclick.net/instream/ad_status.js https://api.segment.io/v1/p https://www.google-analytics.com/analytics.js https://widget.intercom.io/widget/ https://api.mixpanel.com/decide/ https://api.mixpanel.com/track/ https://api.segment.io/v1/t https://api.mixpanel.com/track/
- mirimir 10y ago
  OK, so why the difference? I'm using Firefox 51.0.1 with Privacy Badger 2017.1.26, NoScript 2.9.5.3 and Adblock Plus 2.8.2. Edit: OK, so I had doubleclick.net, facebook.com, google-analytics.com and mxpnl.com untrusted in NoScript. After trusting them all, Privacy Badger still reports no tracking, but lists these trackers: cdn.embedly.com connect.facebook.net www.google-analytics.com fonts.googleapis.com www.google.com Strange. So is Privacy Badger failing to detect tracking?
  - bamboozled 10y ago
    I'm going to take a wild guess here, It's probably NoScript preventing the tracking code form being loaded before ABP can perform detections?
    - mirimir 10y ago
      Well, I did trust/allow domains in NoScript. But I gather that NoScript does other stuff by default. And there's also the fact that I'm blocking WebRTC. Mostly I was just worried that Privacy Badger was failing.
  - navs 10y ago
    Not entirely sure. Could be a side effect of the combination of extensions. On iOS I tend to simply disable javascript. Blocks much of what needs blocking.