Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Windows Terminal Source Code

github.com

Post reply on HN
Print view View original

81–90 of 214 posts

Re: Windows Terminal Source Code

#81

Post by galkk »

dpool wrote: post #65
nyolfen wrote: post #64

winterm looks very nice but it often screws up character alignment if you resize the window. it happens so frequently that i gave it up, because at least once a day i could no longer tell what i was typing or trying to copy. i'm a happy customer with alacritty windows builds, but i wish it had tabs.

You're probably already aware of this, but just in case you're not (or someone else reads this that's curious), running tmux (src: https://github.com/tmux/tmux/wiki ) inside alacritty will give you tab functionality along with the ability to horizontally/vertically split and a host of other fun features.

Is it tmux -CC style of iterm2 or you meant native tmux features?

Re: Windows Terminal Source Code

#82

Post by idatum »

Melatonic wrote: post #25
Bostonian wrote: post #3

Just wondering -- why would Microsoft release the source code for this component of Windows?

Windows in general is moving more in this direction and trying to integrate more with linux

And WSL/2 is a way better experience for me when using Terminal.

And tmux works.

Re: Windows Terminal Source Code

#83

Post by Terry_Roll »

Lammy wrote: post #21
whywhywhywhy wrote: post #10

Earlier quoted context omitted.

ok, what do those do?

There are some pretty detailed comments on many of them if you click through to their call sites, and more can be inferred from the file names of the callers. Let's take a look at `windowio.cpp` for example. This most-generic event fires every time you type any input character on the keyboard: https://github.com/microsoft/terminal/blob/57c3953aca49f68ac... It also has more-specific events for several different ways o…

Isnt that why Windows is called Windows because its a window on their user's life?

Re: Windows Terminal Source Code

#84

Post by judge2020 »

disruptiveink wrote: post #63
babypuncher wrote: post #47

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 don’t see why the makers of an app aren’t entitled to seeing how the app is used for the people who opt to use it. If I’m using windows terminal, I want them to know how often I use the hot keys, how often I split a terminal vertically then horizontally (alt-shift-d), etc. lest it be removed, since I know they don’t have infinite resources to dedicate to this single project to maintain every feature forever and ever.

Re: Windows Terminal Source Code

#86

Post by rstat1 »

imwillofficial wrote: post #80
rstat1 wrote: post #77

Earlier quoted context omitted.

>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.

What is sensitive about knowing some unidentifiable person clicked a button 10 times?

Nothing. Nothing at all.

Re: Windows Terminal Source Code

#87

Post by ridiculous_fish »

Guillaume86 wrote: post #29
Lammy wrote: 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.

It appears to be collecting information like the names of processes which are run. That is well beyond what I would consider acceptable.

https://github.com/microsoft/terminal/blob/57c3953aca49f68ac...

Re: Windows Terminal Source Code

#88

Post by throwaway67743 »

kingcharles wrote: post #46
Bostonian wrote: post #3

Just wondering -- why would Microsoft release the source code for this component of Windows?

Probably the same reason they've opened sourced some other components lately: community feedback and updates. There are a bunch of bugs in Windows core that I can't even get anyone to look at (and I'm an MVP). With these little bits they've opened sourced you can actively participate in helping the team fix the bugs, and add features as needed. I know the team on Terminal had a whole muddle of problems to do with ren…

Why pay employees to fix bugs when some random can fix it for free? It makes perfect corporate business sense. (Not saying its a good thing, but it does make sense from a business POV)

Re: Windows Terminal Source Code

#89

Post by ridiculous_fish »

Genbox wrote: post #75
imwillofficial wrote: post #60

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…

It appears to send back the names of programs, so MS is learning when their users do shady activities (torrenting, youtube-dl) or use competitors' products (aws) or even the names of internal tools.

Re: Windows Terminal Source Code

#90

Post by what-the-grump »

jiggawatts wrote: post #70
Genbox wrote: post #61

Earlier quoted context omitted.

What you are stating is incorrect. Each of the calls you link to sets a boolean here: https://github.com/microsoft/terminal/blob/57c3953aca49f68ac... It does not transmit what you copy, search for or when you clicked/resized/closed the window. It simply stores a true/false value saying "feature X was used". In some cases, like with find/replace, it also stores the average length of things you searched for. That is a…

Every group implements their own telemetry. Every group goes through the same “learning process” of making it asynchronous and correctly dealing with proxies, firewalls, etc… Inevitably mistakes are made that either slow down computers or outright freeze apps that can’t connect to some telemetry endpoint. Security teams around the world feel like they’re holding back the tide with a broom because EVERY piece of softw…

Just FUD?

You are running an operating system made by Microsoft, they could monitor how often you click your mouse just like every website on the planet at this point but dont. Boolean telemetry on feature use is somehow the end of the world? Get out.

Post reply on HN