Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Telemetry not being disabled #16131
Steps to Reproduce:
I have disabled telemetry as described in the FAQ. I have set the following properties in the settings:
Now despite of this, when I log my network traffic (with Wireshark) I can see that Visual Studio Code periodically contacts vortex.data.microsoft.com. This is a known server used for telemetry purposes. I have opted out of the telemetry and information is still sent, why? What information is exchanged?
The FAQ describes:
To me this means that no telemetry connections should be made, because I would assume that continuous connections to the server can still easily be used to collect information for product usage tracking even if no actual private data is being collected by the application itself.
We use our telemetry to help understand how to make the product better – in fact a good example of this right now is some work we are doing to improve performance. So, we appreciate it when users opt to send us telemetry.
That said there are times when people don’t want to do that and you bring up a good point – today we continue to send events stating that a user has
But we don’t need to do that and I don’t think it’s what you expect as a user – so we will stop sending anything i.e. even the
Thanks for bringing this to our attention and I hope you enjoy working with VS Code.
I'll close the issue for now but please fell free to reopen if this is not sufficient.
Sean McBreen – VS Code Team Member
added a commit
Dec 2, 2016
I used to get offline warning, with a stack that it cannot reach
after the restart, within 20 seconds, I get the same warning, but a different stack. It doesn't have any log on contacting
what else need to avoid detecting offline!!!
Version 1.9.1 (1.9.1)
Yeah I was just about to install this but saw the 'data' thing in the terms and service.
I'm cutting windows out of my life for becoming spyware, was going to give VSCode a chance because it's open source. But not if it's just another foothold into the same old game
@bsr203 the message you see comes from the autoupdater. It checks if a newer version of VS Code is available by comparing the commit hash. You can disable it by setting
When you have set
For the record,
I still see connection attempts by Visual Studio Code to
I saw a comment re: this in twitter right now - so wanted to do a quick update...
I'm pretty sure we [VS Code Core] are doing the right thing here and we would love any pointers (all code is OSS).
To be very clear we want to do the right thing (hence my prior comments) and we think we have no gaps.
At the same time there is a chance an extensions send telemetry and that could be the issue here (we are also working hard to ensure any extension created by our team, other teams and others in general do the right ting). But we don't control all of their code - or the world :)
Net, net - if there is a gap help us find it - we don't think we have one but if we do we will close it.
@seanmcbreen We're not talking about that telemetry is bad, but instead, we think that opting out, means, that we do not send ANY analytic. I don't care about your analytic, and you need to accept that, so I only want communication to the Microsoft servers when it is needed(e.g. installing extensions or looking for updates). I do not want to send any further signals.
(Hoping that anyone responds to this)