[stinos]

Such analogies really depend on what the telemetry contains (granted, I don't know in this case). I.e. you describe it as stealing from inside the house. Say, VSCode figuring out your email adress and reporting it. But it might as well actually be pretty anonymous non-personal data i.e. more like looking at the outside of a house and taking note of that. Say, VSCode reporting the theme you use, and just that.

[mosselman]

> Say, VSCode reporting the theme you use, and just that.

Wouldn't that be like looking through the windows to see what clothes they wear or at what time they go to bed or who they sit at the table with?

Just because you are outside of someone's home it doesn't mean you can't invade on their privacy.

Why does an editor need to do telemetry to begin with? Mind your own business. If you don't want to give me something for free, don't. Don't make something free and then feel like you have the right to spy on me. Charge me for using it.

[stinos]

Wouldn't that be like looking through the windows to see what clothes they wear or at what time they go to bed or who they sit at the table with?

Hehe with 'theme' I was actually just thinking about the color of the outer walls, should have made that clear. Even then: passing by a house and peeking through a window once is usually legal and as far as I know doesn't require consent (at least not in my country). Stopping in front of the window and staring inside for hours, not so much. Nor is passing by at the exact same time everyday and peeking inside.

Why does an editor need to do telemetry to begin with? Mind your own business

I'm not advocating in any direction here, be it pro or against telemetry. My point merely is that before making analogies, you'd better first check what telemetry exactly is being collected otherwise your analogy might be completely off.

[jug]

Telemetry is commonly used for statistics on how a product is used, to learn for example if the user interface is counter intuitive or obnoxious with a much better sample size than their own team.

I also note that we still don’t have a clue in this discussion what the telemetry even includes despite tools and probably even documentation detailing this already existing. But I guess it’s more fun to debate this from a philosophical standpoint than the product in question.

[toyg]

From everything I’ve read, MS (and other telemetry-happy developers like JetBrains) see telemetry as a way to gather statistics about UI interaction patterns and popularity of this or that component, so that they can prioritise development towards the most popular features and problems. It’s a bit like our good old “Popularity Contest” package in Linux, but applied to UI elements and behaviours. It’s the sort of thing that resulted in a massive Paste button on the first Office ribbon, because telemetry said Paste was the most used feature.

Sometimes I wonder if I should turn all telemetry on, so that they’d have a datapoint that actually matches my workflow rather than Joe Schmoe’s. It’s a bit invasive though, and culturally speaking is a horrible model (“I can’t change things unless you let me watch what you do all the time”).

Obviously if you care about privacy you should keep telemetry off, but to be honest, if you don’t trust Microsoft to respect common decency about private code, you just shouldn’t use a tool they built in the first place. I use JetBrains tools and trust them enough to leave telemetry on (“voting” for my preferred features, effectively). If you do any politically-sensitive work, though, you should absolutely stay the hell away - because then it doesn’t matter what they do with it today, but what they could do if they wanted (i.e. under pressure from authorities).

[Silhouette]

Obviously if you care about privacy you should keep telemetry off, but to be honest, if you don’t trust Microsoft to respect common decency about private code, you just shouldn’t use a tool they built in the first place.

Isn't that the point of today's discussion: you can use the privacy-respecting alternative instead?

[toyg]

It's still effectively developed by MS, so it might be doing something funky outside of "regular" telemetry and you wouldn't know unless you fully audit the entirety of the codebase.

[Silhouette]

Sure, but now we're comparing an open source product you can build yourself that might be doing something shady but where we have no evidence of that, against a product derived from the open source version that is openly adding privacy-eroding functionality, and with a corresponding privacy policy that is ambiguous at best about how far it will go.

[Silhouette]

I also note that we still don’t have a clue in this discussion what the telemetry even includes despite tools and probably even documentation detailing this already existing.

Unless there are clear statements and guarantees that nothing will change in future updates without the user's express consent, the statements themselves aren't worth much anyway in this kind of discussion.

Microsoft's privacy policies are notoriously opaque, to the point where you'll have trouble verifying that, for example, they aren't granting themselves the right to upload your source code. This observation almost invariably attracts downvotes, but anyone who thinks I'm exaggerating can easily refute the point by citing the places in Microsoft's documentation that say otherwise and guarantee not to change that in the future.

[robalni]

My point is that it's not just what information is being taken that matters. Even if you don't take anything it's still wrong to do things inside someone's computer or home without permission. Maybe VS Code asks for permission properly and gives the user sufficient control and has good defaults, I don't know, but it's difficult to do that properly because people don't understand computers as well as they understand the rest of life.

[ulisesrmzroche]

This (Vscode) is a product for developers, so are you saying that if you use VScode you don’t understand computers?

That’s very arrogant of you

[robalni]

By "computers" I really meant "the complexity in the software that computers run". Computers do very complex things and most of those things can't be directly seen. So if you want to tell someone about what some software is doing, it's not always easy.