Live data from Hacker News

Show HN: Warp, a Rust-based terminal

warp.dev

401–410 of 757 posts

Re: Show HN: Warp, a Rust-based terminal

#401
post #20

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…

How do you check which requests its making? Do you just use tcpdump or something?

You could use a layer 7 firewall for this purpose. I use Little Snitch on macOS and Opensnitch on Linux. Given this application is macOS only right now, I would bet OP used LS since its popular on macOS.

Re: Show HN: Warp, a Rust-based terminal

#402
post #20

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…

I just downloaded it, but then thankfully read this comment before running it. No way do I want my terminal sending stuff to Google.

Exactly the same, clicked "comments" as I was downloading it, saw the first comment, deleted the installer.

I'd be supportive of "report issue" buttons (I'd use them, yes), and occasional "Hey, you've used this app for a week/two/month, may we send some telemetry? We need it to better understand how the app is used. Here's the data, is it OK to upload it?" prompts. Yes, as long as I don't see anything sensitive in the payload - it sure is okay, you respect me and I respect you (with bonus points for politely asking); and I'll be sure to reaching out if I'd see anything sensitive.

Phoning home from the get-go for anything but an anonymous update check and requiring some account is a hard "no".

Re: Show HN: Warp, a Rust-based terminal

#403
A login-required terminal that sends telemetry to multiple sources is on the front page...why? Is it just because it's written in Rust? I don't see any other reason. It's not even fully open source.

> After 20 years of programming, I still find it hard to copy a command’s output; I always forget how to use `tar`; and I always have to relearn how to move my cursor.

Huh? I think if it takes you >20 years to do basic stuff like that, you need to revisit your approach to learning new things. If I play chess for 20 years and still don't know how to move the pieces, it's not the game's fault, it's mine.

Re: Show HN: Warp, a Rust-based terminal

#404
post #379

Earlier quoted context omitted.

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.

Is multiline editing popular/useful? Thus far, the only occasions I've seen it shown is when someone is demonstrating it.

I use the visual-multi plugin [0] all day in vim/neovim.

I don't like using tons of plugins but multi cursor with with selective invocation like the ctrl-d of sublime etc was the main thing I missed when moving to vim. (I use visual block mode too but it's not the same thing).

https://github.com/mg979/vim-visual-multi.git

Re: Show HN: Warp, a Rust-based terminal

#405

Earlier quoted context omitted.

It's just.. an incredibly bad look to have this be the top comment on a post about this while the website claims that "cloud stuff" is opt-in. It's more essential to be honest about this during the beta period than after, so "oh it will be opt in" is a cold comfort, alongside the approximately never-true "we'll open source it some day." Not touching this with a ten foot pole. Not for something as essential to my day…

We tried to be really upfront in the privacy policy: https://www.warp.dev/privacy Opt-in refers to anything that sends any contents of a terminal session to our servers (as opposed to telemetry which is metadata and never contains any terminal input or output). But we hear the feedback and appreciate it.

> Opt-in refers to anything that sends any contents of a terminal session to our servers

There shouldn’t even be the option to opt-in to something so privacy violating.

Having built-in sending of session content means dangerous data exfiltration is always just one bug or accidental click away.

Re: Show HN: Warp, a Rust-based terminal

#407
post #384
post #366

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. Is this really the case? It seems that to find mistakes in software for various interaction patterns, truly exhaustive automated tests would likely work far better by various measures (coverage, reliability, reproducibility, reusability etc.) and at the same time do not have the extreme downside of privacy invasion. For example, see a se…

Automated tests are completely useless for finding (let alone solving) human interaction issues. To compare them with telemetry is a category error.

Re: Show HN: Warp, a Rust-based terminal

#408
post #322

Not much new to say, just my $0.02. - Love the idea overall of a fresh, new shell. I love novelty, features, ergonomics, and this pushes all the right buttons - Looks gorgeous - The mandatory Github login is...weird. I don't mind logging in, but it seemed unskippable, and conceptually that leaves a bad taste. - Mandatory telemetry...ehhh. Like I get it, I use Sentry and OTEL, I love the visibility, and I get exactly…

Appreciate you writing in!

> I would easily pay $20-50 for a souped-up terminal (I spend all day in it), even a closed-source one, but the "we raised tons of money to build a free terminal and haven't figured out how to monetize it yet", again, understandable, but not the best look, given the mandatory data collection. Hey, dev's gotta eat, but I'd rather pay for OSS and transparency, rather than free-but-you-are-the-product, and I hope they go for the former route.

The terminal is totally free for individuals. Our business model is to make the terminal so useful for individuals that their companies will want to pay for the team features.

The general philosophy is that we would never charge for anything a terminal currently does. So no paywalls around SSH or anything like that. The types of features we could eventually charge for are things that have a cost to us, for example enabling real-time terminal collaboration. Even those will likely be free up to some level of usage and only charged in a company context.

We will never sell your data.

> Also the privacy policy doesn't seem to be linked from the app. I can get to it, but would be nice to just go there right from the about page.

The privacy policy is linked from the login screen and it's also one of the first items in our user docs.

Re: Show HN: Warp, a Rust-based terminal

#409

For completions, I would recommend becoming compatible with https://fig.io/ ; perhaps investigating a partnership or even merger with them.

There definitely seems to be overlap here. I'm finding it hard to believe that VCs have backed both these vary similar ideas that seemingly a large portion of their target audience finds objectionable. The HN discussions around Fig have also had a similar negative tone.

Re: Show HN: Warp, a Rust-based terminal

#410

Earlier quoted context omitted.

I understand where you're coming from. My take is that there are plenty of commercial projects that have open source dependencies so it's not quite so black and white. That said we are still figuring out the best way to proceed on open sourcing the warp client code.

Yes there are plenty of those. And if they then blatantly state that they are not open source because they don't want somebody to build a business on their product while that's exactly what they are doing, then they lost me as well. I really like what you guys are working on, and I'd absolutely give it a try. But this is really a deal breaker here. Make the team-oriented features proprietary that need server space an…

As pointed out elsewhere, the product (with waiting list) was announced here 8 months ago where open-sourcing was suggested (privacy and security and all that), but it seems that it hasn't been important to them.
Post reply on HN