Feature #5831

unblocking js: explain to users the risks involved

Added by Anonymous over 2 years ago. Updated over 2 years ago.

Status:NewStart date:09/28/2015
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


Enabling javascript means that sites can track you.
However, js is also extremely widespread and lots of site won't work well/at all without any js.
As such, many users will be tempted to enable js to see the whole site.

As per an IRC discussion with _hc, I suggest adding a small popup/explanation explaining how js makes tracking possible if a user attempts to enable javascript, in order to help people make an informed choice when considering enabling js or not.

Gist of _hc's explanation on IRC:
javascript can generate and report unique IDs based on the browser setup
anyone who can see what the javascript does can track you
if that info is transmitted in plain text, then lots of others can see it
also, anyone with whom that site is sharing data with, like analytics services, etc., can track you
and once you are tracked, you have basically no control over where that info goes
hence, javascript is disabled by default


#1 Updated by axel over 2 years ago

Created this issue without being logged in, recreated it logged in (here: https://dev.guardianproject.info/issues/5832) as I couln't retrieve paternity of this issue.

Please delete this one, cheers :)

Also available in: Atom PDF