Re: [projectvrm] tracking via 3rd party sites, was: [ PFIR ] A former Googler has declared war on ad blockers

[Id Coach < >]

Thanks Don,

On 6/20/15 10:51 AM, Don Marti wrote:
> begin Id Coach quotation of Sat, Jun 20, 2015 at 07:06:42AM -0700:
> > Don,
> >
> > I'd love to implement some of your tools, but why is it necessary to push
> > all our site traffic through your domain?
> An attempt to do fake third-party tracking is the
> only way I know of to reliably detect vulnerability
> to real third-party tracking.
In my case, I have a few domains and can set up one for another.

> > For example, your Check Browser script for footers (every page in a PHP
> > site):
> > ...
> >
> > Both scripts are yours, run at your server, right? I hesitate to push all my
> > (small site's) traffic through any third-party sites for reasons of
> > transparency and control. That IS part of the problem imho.
> I agree.  If it's possible to make a system for
> warning about third party-tracking that can run on
> the same domain, I'll make that instead.
>
> Want to host your own copy of
> www.aloodo.com/protection/ ? If so, please let me
> know and I'll put it under a Creative Commons license.
> That page can be copied easily.  Or link to your own
> page of tracking protection recommendations.
Yes please

> The other part is harder.  Think of the
> "ad.aloodo.com" domain as something like an EICAR
> Test File for web tracking.
>
>    https://en.wikipedia.org/wiki/EICAR_test_file
>
> ad.aloodo.com is listed in the Disconnect and
> EasyPrivacy blocklists, and I have requests pending
> for Ghostery and Blur.
>
> If one of your users has a browser set up with most
> kinds of basic tracking protection (IE with the
> EasyPrivacy TPL, Firefox with tracking protection on,
> Apple Safari with the default out-of-the-box settings,
> or Privacy Badger, or AVG Crumble), that browser
> either won't set the ad.aloodo.com cookie or won't
> connect to ad.aloodo.com at all.
>
> Don

Ok, that's interesting and helpful to know. Thanks.

  judi