Live data from Hacker News

VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

github.com

41–50 of 120 posts

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#41
post #14

Finally. It obviously is something that flies over the heads of most people here at least by reading the comments. This is great.

I don’t personally see the need, but the fact that someone can do this should at least once and for all settle how “real” the open-sourceyness of VSCode is.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#42
post #7

Earlier quoted context omitted.

Doesn't it suffice to set the following in your User Settings? "telemetry.enableTelemetry": false Honestly I'm very happy to give telemetry data. Microsoft is doing so much to improve the experience, they can make it better with some data.

This doesn't suffice unfortunately. That setting has worked inconsistently, or not at all, and add far as I've seen in my own testing it never disables all telemetry. There have been issues open on GitHub about this for a long time, though it's a few months since I checked there for updates (I stopped bothering and just put it in my firewall rules; I still see blocked connections in thy log today). I'm a very happy v…

Are you sure the additional telemetry isn’t from extensions? Our extensions (Salesforce) have our own telemetry setting, but we do also respect the global VSCode setting due to this exact possibility of confusion. However, I know that there are other extensions that dont respect the global setting.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#43

Earlier quoted context omitted.

This doesn't suffice unfortunately. That setting has worked inconsistently, or not at all, and add far as I've seen in my own testing it never disables all telemetry. There have been issues open on GitHub about this for a long time, though it's a few months since I checked there for updates (I stopped bothering and just put it in my firewall rules; I still see blocked connections in thy log today). I'm a very happy v…

> @bunderbunder I bet it's still nothing compared to the level of data collection that a typical website does these days. I'd say the opposite. Consider that (a) you typically visit websites briefly and periodically while most vscode users have it open as long as their computer is on, and (b) Electron provides access to lot more device data than the browser sandbox. The reason websites tend to have such far-reaching…

Another big difference, though, is that VSCode's telemetry is publicly documented.

So, regardless of what they're able to collect, I know what they are collecting, and how personally identifiable it is, and I know that it's pretty tame compared to what I've seen elsewhere.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#44
post #31

Doesn't have the latest build for macOS. :(

Disclaimer: general comment. Not affiliated with project, etc.

I don’t know about you, but I don’t typically feel like shelling out $1000 to buy a machine specifically for an OS I don’t use, just to build a binary to non-paying users of free software.

If Apple would provide easily installable ISOs for VBox/VMWare installations (or something equivalent), I might bother setting up a build for it.

Right now it’s out of the question.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#45

Earlier quoted context omitted.

This doesn't suffice unfortunately. That setting has worked inconsistently, or not at all, and add far as I've seen in my own testing it never disables all telemetry. There have been issues open on GitHub about this for a long time, though it's a few months since I checked there for updates (I stopped bothering and just put it in my firewall rules; I still see blocked connections in thy log today). I'm a very happy v…

Are you sure the additional telemetry isn’t from extensions? Our extensions (Salesforce) have our own telemetry setting, but we do also respect the global VSCode setting due to this exact possibility of confusion. However, I know that there are other extensions that dont respect the global setting.

I tested without extensions back when I was following the open GH issues, so that wasn't the case then.

It could be that MS fixed the issue since, and the connections I see in logs now are from extensions, but I also presume this isn't the case as my firewall rules are IP-based rather than purely app based (since the latter would kill the market browsing functionality).

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#46
post #7

Earlier quoted context omitted.

Doesn't it suffice to set the following in your User Settings? "telemetry.enableTelemetry": false Honestly I'm very happy to give telemetry data. Microsoft is doing so much to improve the experience, they can make it better with some data.

This doesn't suffice unfortunately. That setting has worked inconsistently, or not at all, and add far as I've seen in my own testing it never disables all telemetry. There have been issues open on GitHub about this for a long time, though it's a few months since I checked there for updates (I stopped bothering and just put it in my firewall rules; I still see blocked connections in thy log today). I'm a very happy v…

Can you share the firewall rules/domains to block to disable telemetry for VSCode?

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#47

Earlier quoted context omitted.

> @bunderbunder I bet it's still nothing compared to the level of data collection that a typical website does these days. I'd say the opposite. Consider that (a) you typically visit websites briefly and periodically while most vscode users have it open as long as their computer is on, and (b) Electron provides access to lot more device data than the browser sandbox. The reason websites tend to have such far-reaching…

Another big difference, though, is that VSCode's telemetry is publicly documented. So, regardless of what they're able to collect, I know what they are collecting, and how personally identifiable it is, and I know that it's pretty tame compared to what I've seen elsewhere.

Ah, that is a fair point. I hadn't looked at what they collect, I was just speculating about what they could collect if desired.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#48
post #7
post #3

Earlier quoted context omitted.

For me, it's more about telemetry than licensing.

Doesn't it suffice to set the following in your User Settings? "telemetry.enableTelemetry": false Honestly I'm very happy to give telemetry data. Microsoft is doing so much to improve the experience, they can make it better with some data.

Telemetry should not be on by default without express user consent.

Re: VSCodium: Binary releases of VSCode without MS branding, telemetry and licensing

#50
post #34

I appreciate this effort and am not suggesting it's not necessary. Just curious: are there any known ill-desired effects of the MS binaries? My understanding is that it's just branding and telemetry that can be turned off.

They can't be distributed in distro package managers which usually require everything to be foss.

Depends on the distro. For the main Debian repos, it's true. Others like Arch are more lenient, e.g. Arch packages the Steam client.
Post reply on HN