News for hackers. Stuff that matters.
Re:EFF's Panopticlick 2.0 Launches with Tracker Protection T... by Dylan16807 on Thursday December 17, 2015 @02:55PM (#10754022)
That was weird, the no-js version didn't work. It just sat there spinning.

>Does your browser unblock 3rd parties that promise to honor Do Not Track? X no

What, why would I unblock those?

Edit: Thanks HN for deleting the fancy X unicode!

Re:EFF's Panopticlick 2.0 Launches with Tracker Protection T... by pde3 on Thursday December 17, 2015 @03:07PM (#10754132)
> That was weird, the no-js version didn't work. It just sat there spinning.

What extensions do you have installed? There's a known and unfixable issue with browsers that both block JS and absolutely block all requests to tracking domains (eg AdAway, which modifies /etc/hosts).

> What, why would I unblock those?

To incentivise better behaviour by web publishers and advertisers!

Re:EFF's Panopticlick 2.0 Launches with Tracker Protection T... by Dylan16807 on Thursday December 17, 2015 @03:17PM (#10754199)
ublock was stopping requests to third parties. Though the javascript version didn't care that third party requests were blocked, only the no-js version.

It's kind of weird for something specifically dedicated to measuring tracking to get so confused by an anti-tracking mechanism.

> To incentivise better behaviour by web publishers and advertisers!

Maybe if it could have some legal teeth to it, otherwise it's too easy to lie to get your tracker unblocked.

Re:EFF's Panopticlick 2.0 Launches with Tracker Protection T... by dandelion_lover on Thursday December 17, 2015 @03:18PM (#10754213)
>To incentivise better behaviour by web publishers and advertisers!

I switched off "Do Not Track" in my options since only good-behaving websites listen to it, such as those using Piwik analytics, which respects privacy. Therefore I only would harm good people with Do Not Track on.

Re:EFF's Panopticlick 2.0 Launches with Tracker Protection T... by legind on Thursday December 17, 2015 @03:04PM (#10754104)
With certain rare configurations (if you have a domain-based blacklist blocker and javascript disabled) this may occur. I suggest turning your js back on just for the test.