4 ms·

Thanks for the feedback - I'm the founder at Warp. There was a ton of discussion on this yesterday with our ShowHN [0] and we are considering what changes to m

Thanks for the feedback - I'm the founder at Warp. There was a ton of discussion on this yesterday with our ShowHN [0] and we are considering what changes to make based on the feedback (some of which are inline with your suggestions). We do publish all the telemetry we collect here: https://docs.warp.dev/getting-started/privacy#exhaustive-telemetry-table https://docs.warp.dev/getting-started/privacy#exhaustive-tel... And we are committed to making telemetry optional when we leave beta. And it's definitely the case that command input / output are never sent to the server. Login is a bit trickier as it's hard to build an app that leverages the internet and facilitates teamwork without understanding user identity. But point taken. [0] https://news.ycombinator.com/item?id=30921231 https://news.ycombinator.com/item?id=30921231

xg15 5y ago
> Login is a bit trickier as it's hard to build an app that leverages the internet and facilitates teamwork without understanding user identity. But point taken. I thought the team/collab functions would just be optional features. First and foremost, isn't this a terminal still?
Mo3 5y ago
> Login is a bit trickier as it's hard to build an app that leverages the internet and facilitates teamwork without understanding user identity. But point taken. I think you need to understand that this is a rare edge case and at least 95-99% of users do not want or need this. A terminal is a terminal, a command line shell. There are countless tools within it that have been developed for decades that provide collaboration: Git is a nice example. The shell itself is localized and user authentication is handled by the system. What exactly is there to be worked on in collaboration on a command line? Only one person can type or execute commands on it at the same time, and even worse, it is a very sensitive part of any system and the whole point of TTY and session management is to NOT have it as a shared resource. Don't get me wrong, there are features of your product that look very nice and have almost convinced me to switch to it (until I saw the SSO screen), but the way you approach this rings all possible alarm bells and demonstrates a deep and fundamental lack of understanding of what you are trying to re-invent.

xg15 5y ago

> Login is a bit trickier as it's hard to build an app that leverages the internet and facilitates teamwork without understanding user identity. But point taken. I thought the team/collab functions would just be optional features. First and foremost, isn't this a terminal still?

Mo3 5y ago

> Login is a bit trickier as it's hard to build an app that leverages the internet and facilitates teamwork without understanding user identity. But point taken. I think you need to understand that this is a rare edge case and at least 95-99% of users do not want or need this. A terminal is a terminal, a command line shell. There are countless tools within it that have been developed for decades that provide collaboration: Git is a nice example. The shell itself is localized and user authentication is handled by the system. What exactly is there to be worked on in collaboration on a command line? Only one person can type or execute commands on it at the same time, and even worse, it is a very sensitive part of any system and the whole point of TTY and session management is to NOT have it as a shared resource. Don't get me wrong, there are features of your product that look very nice and have almost convinced me to switch to it (until I saw the SSO screen), but the way you approach this rings all possible alarm bells and demonstrates a deep and fundamental lack of understanding of what you are trying to re-invent.