Proprietary closed-sourced crapware.
Show HN: Warp, a Rust-based terminal
601–610 of 757 posts
Re: Show HN: Warp, a Rust-based terminal
#602Earlier quoted context omitted.
Hi - as the poster and founder I again completely get the concern. We should make it even more transparent what we collect. You can see it here: https://docs.warp.dev/getting-started/privacy#exhaustive-tel... Re: big business, we're still pretty small, but it's true that we are trying to build a business around the command-line. I get that's controversial and it's not something that exists and that the terminal is a…
As much as I can appreciate the community’s reaction to your approach of default collection of telemetry, I can also equally appreciate you and the rest of the team sucking it up and accepting the feedback. Thanks for that, and I’m personally interested to see where you’re able to take Warp. I think there’s something potentially pretty compelling here. My advice here would be to simply make telemetry opt-in during th…
If the code is there, it is potentially exploitable. So, opt out is nowhere near good enough. If it can send to remote hosts, this can be abused. This capability should not be there, at all.
Look at the recent logging fiasco for an example.
Re: Show HN: Warp, a Rust-based terminal
#603Earlier quoted context omitted.
Automated tests are completely useless for finding (let alone solving ) human interaction issues. To compare them with telemetry is a category error.
Shouldn't human interaction errors be left up to the user to report, as opposed to software sending sensitive information to a third-party?
I'm with you on not sending data, but have you ever read user reports? IF you get any (most won't report) they likely won't have enough information to reproduce or fix.
Automated Error reporting does has it uses.
Re: Show HN: Warp, a Rust-based terminal
#604Earlier quoted context omitted.
I'm not sure I'm ready to have SaaS models replace core utilities and tools locally. > Announcing Warp’s Series A: $17M to build a better terminal And just thinking about this... it's not clear to me what their moat will be as I suspect if there's a really compelling feature it will be available in OSS terminals quite quickly. Perhaps it's the product polish? But I'm not sure polish is what I want from a terminal, at…
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.
Multiline works out of box in fish shell.
I'm not sure how terminal is relevant here.
Re: Show HN: Warp, a Rust-based terminal
#605Like others here, I'm leery of replacing my terminal with a VC-backed, maybe open-sourced eventually product, and a bit annoyed it claimed a name already in use in the Rust world. But...it is exciting to see someone reimagining the terminal a bit. People frequently talk about wanting a better GUI interaction model for everyone, but the actual ideas to improve it seem to be missing, I think because the desktop status…
I'm working on a terminal browser of sorts that is designed to browse terminal user interfaces served by servers. The idea is that no mouse input is supported and servers specify keyStrokes for links. It starts from a protobuf specification optimized for sending components over gRPC in a pageRequest/pageResponse manner. In order to promote the idea I've been spending most of the time writing a client in Go. I think i…
This sounds like ssh apps via https://charm.sh
Re: Show HN: Warp, a Rust-based terminal
#606Wanted 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…
As the author of the post, I think this is totally reasonable feedback and something we have discussed quite a bit on the team. The general stance on telemetry that we have is that a) we are just starting and it's really helpful to see which of our product ideas are useful to our users (e.g. does anyone use AI Command Search? Should we continue to invest in it) b) we tried to be very explicit about what we are and ar…
As a Sentry user (for a web app where people are not placing sensitive IP!) - it is INCREDIBLY easy for it to be configured to suck up massive amounts of PII and sensitive IP in the context of its crash reports. If I am running `kubectl create secret --from-literal` and something crashes, can you guarantee that the contents of that command will not be loaded into Sentry? Breaching this guarantee would be as simple as having some code somewhere in your stack (including a parsing library) format an Error with the command contents, miles away from anything Sentry-specific.
I'd be much more trustful of your product (and indeed, I do desperately need a better terminal!) if you were to:
- make Sentry crash reporting opt-in (or at the very least have a popup that occurs with the content of what will be sent to Sentry before anything is sent to Sentry), AND
- clarify in your event telemetry documentation, and explicitly in your Privacy Policy, that ONLY the event ID/name, timing, and the user ID are sent to Segment, nothing else.
But I simply cannot use a terminal where my keystrokes might be logged to anyone's Sentry or Segment account - even if it were our company's own Sentry account. The risk of partner-entrusted credential leakage into an insecure environment is simply too high.
Re: Show HN: Warp, a Rust-based terminal
#607Wanted 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…
As the author of the post, I think this is totally reasonable feedback and something we have discussed quite a bit on the team. The general stance on telemetry that we have is that a) we are just starting and it's really helpful to see which of our product ideas are useful to our users (e.g. does anyone use AI Command Search? Should we continue to invest in it) b) we tried to be very explicit about what we are and ar…
Is this answer minimizing a bit?
You can use the Firebase login tools without the person identification stuff pulled in. Note that for companies failing to do this in a privacy respecting way, a savvy user can usually get granular at the firewall and get the login to work without the audience reporting. Which means you could…
Similarly, in my book, segment.io isn’t just “telemetry” so much as it’s killer feature of cross app audience persona correlation, so less about what’s up with the app, more trying to learn more about the users without asking them. If you were instrumenting the app UX and not trying to see who is using you, there are other choices.
A number of ways to do accounts that can leverage a person’s own IdP or other approaches where you don’t have to have accounts, e.g. most any channel the team or group can access will do to get in sync on a session start.
Regardless, and even if GitHub and e.g GitHub Orgs are your way, all of them should be optional since not everyone is desperate to team their cli.
Last, and sorry to put it like this, if you’ve “discussed it quite a bit” as a team, I’m not sure but maybe that gives me less confidence in your respect for security, privacy, and users.
I’d imagine that deliberate discussion backed by respect for your users and team know-how should have resulted in a different set of choices.
Re: Show HN: Warp, a Rust-based terminal
#608Earlier quoted context omitted.
Just curious, what tools do you prefer to use to identify network requests from recently installed applications such as this?
I can't imagine using a Mac without Little Snitch: https://obdev.at/products/littlesnitch Among other things, it is disturbing how chatty a lot of things are. (Did you know Apple Mail keeps track of which account you email different people with and wants to send that to configuration.apple.com, even if you have carefully disabled everything Icloud related?) There's a similar tool for Linux, but I usually keep a netwo…
Closed source, monitors everything on the machine.
How much do you trust little snitch?
And then asking to keep a copy of your drivers license for ten years is a complete non starter. (Yes, that's in their privacy policy)
Re: Show HN: Warp, a Rust-based terminal
#609Is it written in Rust?
Re: Show HN: Warp, a Rust-based terminal
#610Earlier quoted context omitted.
In addition to crashes, we also want to know things like: which features people are using so we can invest more in them, how much people are using the app so we know if we're doing in a good job. Totally understand if you're not comfortable with that though! It will be removed when Warp is out of the beta test.
I know it sounds logical to you, but the further down that road you go the worse your software will be in the end. Make software with a coherent vision and you can pick and choose features based on how will they fit that vision without needing to spy on your users, or turn it into a popularity contest. Incidentally, you might be interested to know that in the last 8 hours my comment has gotten 25 upvotes; that’s a lo…
> Incidentally, you might be interested to know that in the last 8 hours my comment has gotten 25 upvotes; that’s a lot of lost customers.
No, that's a lot of people who upvoted your comment.
I'd wager anyone who agrees with your perspective is unlikely to have been a Warp customer in the first place.
(Speaking as one who tends towards your side of this discussion.)