Hacker News Reader

Hacker News

Comment by gerbilly | Hacker News Reader

Parent Full thread

gerbilly

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.

View on HN

pbcopy/pbpaste are gems that more Mac users need to know about. A command line interface for your clipboard is invaluable and really ties together jumps from UI to CLI.

Regarding the other thoughts in this post, I have to agree. I use iTerm instead of Terminal.app, but if I had even the remotest fear that it was sending anything elsewhere, I would jump ship. My terminal has all kinds of information that can act on my behalf, and I wouldn't want any of it leaving my Mac at all, ever, period. Had this been open-ish source but not phoned home, I'd give it a try. But opaque data leaving for who knows where? Nope.

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.

Try this: https://github.com/bradwood/glsnip

Disclaimer: I wrote it

sadly, this looks like it doesn't work on iOS, which is my major driver to use pbcopy/pbpaste.

This is... actually genius. I wonder if that would work with media too, specifying the input type or something, going to test that.

Looks easy. Yet you need to write the JPG to a temp file first since applescript does not seem to be able to parse JPEG without seek(), hence no piping / streaming possible.

  [1] https://stackoverflow.com/a/30578507/5094001

same - I'll stick with iTerm and zsh. It's definitely interesting though. Probably a security nightmare though. I noticed the one feature to share terminal output via a third party link. I can imagine there being a set of people accidentally leaking critical information via this feature (ie, passwords, private keys, system settings).

Lots of CLI tools phone home unfortunately. I mean, snap has a cli.. :) Maybe that's low hanging fruit.

1. CLI != CLI tool != terminal emulator

2. Snap is a package manager. All package managers phone home by design, because they make requests to external servers on the user's behalf. If you invoke Snap then you are most likely aware of what it does and how it behaves.

3. I would argue that a lot of CLI tools don't phone home actually. You're right that some do, but the majority of shell utilities are designed to operate on stdin/stdout/stderr. They have no need for network access, and very few utilities come to mind that perform the same degree of data collection as Warp. Certainly no terminal emulators come to mind.

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.

Nope. I have never used Windows on any of my personal machines, not ever. I am waiting this MS Windows thing out, you could say.

At work I have used it in some cases when not given the choice.

If some company I am working for is fine with the Windows CLIs telemetry, then I suppose it is up to them, although I'd argue against it.

In an (absurd-ish) defense of macOS, I don't believe anyone really uses the built-in Terminal and grabs an alternative (often iTerm2).

There's also the rumor that Terminal in macOS has had a handful of developers working on it, at best, over the years. I would bet money that Apple doesn't care enough about it to bother with telemetry and/or privacy policies for it.

I bet that's true. MacOS terminal is basically still the one from next step. They've kept it up to date with changes like GUI toolkits and added a few minor things like tabs. But that's about it.

Fwiw I never bothered with iTerm, Terminal is good enough for me. It even supports some old school vt100 stuff like double width and height fonts. It's one of the better vt100 compatible ones.

I still find macOS Terminal to be noticeably faster than item. At displaying my keyboard input and shell output. It lacks other features, namely split windows, that move me to iTerm, but I do like how fast Terminal is.

> There's also the rumor that Terminal in macOS has had a handful of developers working on it, at best, over the years.

This but every app on the mac that isn't Safari.

>This but every app on the mac that isn't Safari.

Eh, I know it's a joke but there are full teams who work on Pages/Numbers/etc.

I used iTerm from 2010-2018, but then I saw a respected colleague not using iTerm, so I decided to try out the Terminal.app bundled with macOS. It actually works fine, the only difference is that it never gets slow and is available on ever mac machine.

Nothing wrong with the macOS stock terminal too. GP just pulled the macOS terminal telemetry nonsense out of thin air.

I too use iTerm for its rich features, but the stock terminal is known to have lower latency [1] so some people might prefer that.

[1]: https://danluu.com/term-latency/

I have been using the built-in macOS terminal every day for years now.

I have been an OS X user since its inception, and have only ever used the built in terminal. I spend a ton of time in the terminal and I have never felt the need to use anything else.

It’s the only terminal I use on macOS. It’s a really “gets out of your way” piece of software. And super closed source.

Yes, they never substantially upgraded it once it hit 1.0 about two decades ago.

i have been using the macOS Terminal since macOS X was a thing (with different capitalization) and since its origins in NeXTstep since around 1990.

I suspect it's the same codebase, but don't have a proof of that.

Exactly, that's why people tend not to choose Windows for development unless they're forced to.

edit: use -> choose

> Exactly, that's why people tend not to choose Windows for development unless they're forced to.

In my experience, most people who are developing software for Windows choose to use it to develop that software. There are a great many people who choose to develop software for Windows.

Well, that's obvious. If I had to develop software for windows (or OSX) then I'd be using those platforms to build/test those tools.

But I choose not to.

This is so far from truth it's hilarious.

> I suspect OSX is no different and has similar telemetry and privacy policy for its terminal

wrong, Apple isn't Microsoft

No. I don't use Windows. Or OS X.

> Do you use Windows?

Whenever I do that, I can never decide whether it's me who's using Windows or Windows that's using me :-(

> forgets linux exists

Would you expect anything less than a product from the first company to lie down for the NSA?

Note that this is Windows Terminal, not the default terminal that actually ships with Windows (unless that has changed in Windows 11?)

But Windows Terminal is open-source and probably someday community will fork it to remove telemetry the way they did with VSCode.

Reply on news.ycombinator.com