Top
Best
New

Posted by RubyGuy 21 hours ago

Do_not_track(donottrack.sh)
408 points | 126 commentspage 4
dubious2 12 hours ago||
I'm old enough to remember Nancy Reagan just say no!I think this has the same effect.
dnnddidiej 14 hours ago||
Love the idea but is an env var enough. Are there some sessions (docker?) that may not get it.

I'd prefer TRACK_ME as an opt in.

amelius 18 hours ago||
You can also use network namespaces to simply block internet access for certain processes. It can even be finetuned with whitelists or blacklists.
mmooss 17 hours ago|
Could you provide more details? Many applications use multiple processes, and use some intermittently. It seems like quite a bit of work to enumerate every process used and then to keep the white/blacklist updated as usage and software changes - every new application or command you use, every update, every OS change that affects networking or system calls etc ...
amelius 17 hours ago||
Yes, with security comes inconvenience, this is inevitable.

I'm not a daily user of network namespaces, and would probably write a script to do the configuration within a shell (it works a bit like containers). The configuration is inherited by child processes, so you only have to do it once. Basically whitelist the urls you typically use, and maybe let the script popup a dialog asking you to allow access when the firewall catches a domain that is not in the whitelist yet.

darkhelmet 8 hours ago||
I have some issue with how some of these are represented. For example, syncthing has an explicit opt-in request for telemetry / analytics. The suggested setting change is something entirely different - a call to ask what the latest version is. Granted, that server could log your IP address but that's no different to how it uses the relay and discovery servers that are also run by the same people - those could log the same way.

.. which is entirely different to the telemetry system where usage stats are reported. You can see that on data.syncthing.net. But again, thats a separate opt-in. The suggested env variable on the site won't turn that off.

hedayet 16 hours ago||
I'd be interested in, 1. a SOME-TRUST model: a list of opt-outs for the known software that collect telemetry; so that I can just paste that into an env file and be done with it. 2. a ZERO-TRUST model [preferable]: where I control if an application can send any telemetry data; instead of depending on a flag that the distributor may or may not respect.
ninjahawk1 18 hours ago||
Privacy should be treated as a right, not something that can be abused for money. Love the idea of this
joshka 14 hours ago||
It feels like this should be no_track, for consistency with no_color
kstrauser 18 hours ago||
I’m morally opposed to the notion of optimizing the opt-out mechanism. I want a standardized opt-in mechanism, like:

  export ALLOW_TRACKING=telemetry,crash_dumps
and the absence of such a setting means “fuck off, don’t spy on me”. It’s not my responsibility to turn off apps wanting to track me. It’s their responsibility to get me to authorize their specific flavor of tracking.
cj 18 hours ago|
> It’s their responsibility to get me to authorize their specific flavor of tracking.

And they do by burying it in the user agreement you probably agreed to.

Like it or not, it is your responsibility. I agree it shouldn’t be, but let’s be realistic.

msla 18 hours ago||
Then it's my responsibility to feed them fake data.

They didn't opt out of my data, after all.

internetguy 12 hours ago|
https://xkcd.com/927/
More comments...