Live data from Hacker News

Windows Terminal Source Code

github.com

71–80 of 214 posts

Re: Windows Terminal Source Code

#71

Earlier quoted context omitted.

We have a habit of diluting words to the point where they are meaningless, and I think it does more to hurt important causes than support them. By labeling all forms of telemetry as "spying", we just make it so people are less likely to take actual claims of spying seriously.

That is what it once meant. "Spyware" was the term used for any process that called home regarding any information about you, your computer or your usage in the background. Calling home for anything other than "Check for updates" menu items or other actions where calling home was the explicit action the user wanted would get your name tarnished in the media and added to the signature list of software built for the so…

I would call that malware. Telemetry is just malware with a marketing department.

Re: Windows Terminal Source Code

#73

Earlier quoted context omitted.

Just glancing through them it looks like perfectly reasonable telemetry collection, not sure why you call that spying.

Terminals should not be sending telemetry. Imagine if every .exe and every .dll did that! That's not OK!

What about every .com, .pif, .bat and .scr?

Awful.

Maybe quit using file extensions instead of calling things libraries and executables?

Re: Windows Terminal Source Code

#74
post #6

Here are all the ways it spies on you: https://github.com/microsoft/terminal/search?q=Telemetry%3A%... https://github.com/microsoft/terminal/blob/main/src/host/tel...

as a software dev you know that soft anonymous telemetry of how a user use what you do is very valuable to make decision on how to make things.... I wish there was way everywhere to collect with privacy and being accepted by user as not something we want to spie people on... but as always there is (a lot ) of abuse in this area so this may never going to happen

Well if my only choice is 'send arbitrary information on what I'm doing' and 'don't send any information' I'm always going to pick the latter.

Has anyone tried just showing people the information the application would like to report back? I know it's been tried with crash reports.

Re: Windows Terminal Source Code

#75
post #50

Earlier quoted context omitted.

That is not how telemetry works. It is not spying or a privacy issue. Categorizing it as such only dilute the meaning of both terms so the real issues won't be taken serious. If you feel like a bunch of developers getting info about how many times the world clicks on a button hurts you personally, then don't install it. Calling it a privacy issue it taking it too far.

It is absolutely both a spying and privacy issue. What I decide is private, or what information constitutes spying is arbitrary. I love windows terminal, but it should collect nothing by default. Another subjective opinion.

Arh yes, the good old "everything means nothing" argument. I'm sorry to say, but words have meaning [1][2], and most of them are formally defined.

And yes, I think that an HTTP POST to Microsoft's Windows Terminal team saying "UserUsedTerminalInInterative = true" is not a privacy issue, nor is it spying.

Can you explain to me how this information hurt users of Windows Terminal? If it indeed is spying, it should be possible to demonstrate how it is used for hostile purposes or why such an innocuous piece of information must be kept a secret.

Until then, I think it is fair for the Windows Terminal team to collect such basic telemetry for their software

[1]https://www.merriam-webster.com/dictionary/spying

[2]https://www.merriam-webster.com/dictionary/privacy

Re: Windows Terminal Source Code

#76
post #6

Here are all the ways it spies on you: https://github.com/microsoft/terminal/search?q=Telemetry%3A%... https://github.com/microsoft/terminal/blob/main/src/host/tel...

Just glancing through them it looks like perfectly reasonable telemetry collection, not sure why you call that spying.

What's wrong with spying.

But seriously, since Microsoft is sharing the source code, why not just remove the unwanted telemetry and re-compile.

How easy would that be.

Re: Windows Terminal Source Code

#77
post #50

Earlier quoted context omitted.

That is not how telemetry works. It is not spying or a privacy issue. Categorizing it as such only dilute the meaning of both terms so the real issues won't be taken serious. If you feel like a bunch of developers getting info about how many times the world clicks on a button hurts you personally, then don't install it. Calling it a privacy issue it taking it too far.

It is absolutely both a spying and privacy issue. What I decide is private, or what information constitutes spying is arbitrary. I love windows terminal, but it should collect nothing by default. Another subjective opinion.

>what information constitutes spying is arbitrary

No it isn't.

The word "spy" has a very specific definition, that you'd have stretch pretty far to include any of the data collected by the Terminal app.

Re: Windows Terminal Source Code

#78
post #2

this caught my eye: >>Installing and running Windows Terminal Note: Windows Terminal requires Windows 10 2004 (build 19041) or later Microsoft Store [Recommended] Install the Windows Terminal from the Microsoft Store. This allows you to always be on the latest version when we release new builds with automatic upgrades. This is our preferred method. Other install methods Via GitHub For users who are unable to install…

My preferred method would be

    choco install microsoft-windows-terminal

Re: Windows Terminal Source Code

#79
post #75

Earlier quoted context omitted.

It is absolutely both a spying and privacy issue. What I decide is private, or what information constitutes spying is arbitrary. I love windows terminal, but it should collect nothing by default. Another subjective opinion.

Arh yes, the good old "everything means nothing" argument. I'm sorry to say, but words have meaning [1][2], and most of them are formally defined. And yes, I think that an HTTP POST to Microsoft's Windows Terminal team saying "UserUsedTerminalInInterative = true" is not a privacy issue, nor is it spying. Can you explain to me how this information hurt users of Windows Terminal? If it indeed is spying, it should be po…

What a low effort comment.

Yes, words have meanings.

Company A May decide telemetry exposes too much internal information to a potential competitor.

Company B May decide that telemetry does not release anything they want kept secret.

Those are subjective opinions. If I want the data to be kept secret and somebody takes it without my explicit approval, that is a privacy violation. If I don’t care, it’s not. Same thing with spying. If I deem it a secret, it is now spying to take it from me.

Re: Windows Terminal Source Code

#80
post #77

Earlier quoted context omitted.

It is absolutely both a spying and privacy issue. What I decide is private, or what information constitutes spying is arbitrary. I love windows terminal, but it should collect nothing by default. Another subjective opinion.

>what information constitutes spying is arbitrary No it isn't. The word "spy" has a very specific definition, that you'd have stretch pretty far to include any of the data collected by the Terminal app.

No you wouldn’t. It is taking data you haven’t explicitly approved for release. Potential sensitive info.

That is the definition of spying.

You know most of what an actual spy collects isn’t super secret stuff right? Aggregated unclassified information can still reveal secrets.

Post reply on HN