Console Do Not Track – Proposal for a standard environment variable
consoledonottrack.com
Console Do Not Track – Proposal for a standard environment variable
1–10 of 352 posts
Re: Console Do Not Track – Proposal for a standard environment variable
#2This project looks especially relevant because of recent news about Audacity adding telemetry to their project [1] and because of the the community's reaction and a fork [2].
I feel like many people aren't aware that popular open source tools already collect usage data.
Re: Console Do Not Track – Proposal for a standard environment variable
#3I support this fully and I'm very disappointed that the maintainers of these projects are hesitant to adopting it, many citing that they'd be interested only if other major players adopt it first.
Cmon, it's such a minor change. Getting these PR's in means _you are_ a major player (atleast to some) and you might be able to drive change in a positive way. Why not jump on the opportunity?
Re: Console Do Not Track – Proposal for a standard environment variable
#4This is negative consent. I can't fathom why we are supposed to be ok with that.
The variable should be named DO_TRACK.
Re: Console Do Not Track – Proposal for a standard environment variable
#5This is negative consent. I can't fathom why we are supposed to be ok with that. The variable should be named DO_TRACK.
Indeed. And don’t such tools require GDPR consent to allow tracking or processing PII?
Re: Console Do Not Track – Proposal for a standard environment variable
#6I support this fully and I'm very disappointed that the maintainers of these projects are hesitant to adopting it, many citing that they'd be interested only if other major players adopt it first. Cmon, it's such a minor change. Getting these PR's in means _you are_ a major player (atleast to some) and you might be able to drive change in a positive way. Why not jump on the opportunity?
Let's add some competitive pressure: start forking projects that don't support it.
Re: Console Do Not Track – Proposal for a standard environment variable
#7This is from 2019, should be flagged as such.
Re: Console Do Not Track – Proposal for a standard environment variable
#8This is negative consent. I can't fathom why we are supposed to be ok with that. The variable should be named DO_TRACK.
Indeed. And don’t such tools require GDPR consent to allow tracking or processing PII?
This is a great point actually - but it probably depends on if the data is regarded as "personal data" or not. IP-addresses is considered sensitive which would mean that if they're saving that it is probably not ok. I'm not a lawyer though :)
Re: Console Do Not Track – Proposal for a standard environment variable
#9This is a great idea, but I feel like it needs an adoption and roll out strategy so that is starts to snowball.
I think that opening PRS makes a lot of sense, but smaller projects or projects that don't yet have an opt-out mechanism are the most likely to adopt it in the early days I think. Then once you gather some momentum around those bigger projects might follow suit.
Re: Console Do Not Track – Proposal for a standard environment variable
#10This is negative consent. I can't fathom why we are supposed to be ok with that. The variable should be named DO_TRACK.
I see where you are coming from, but realistically this will have better chances of being adapted. Also the "do not track" term is already a thing for browsers, so might just stick with it.