Show HN: Warp – Secure and simple terminal sharing
github.com
github.com
Edit: Reading through some of the replies here it might actually be using their servers at least for the ID resolution.
This gives you 2 ssh addresses (read only and read write) that you can send out.
This looks like a great project and I'll be keeping my eye on it, but there's no reason for me to switch to this and lose out on features.
It's open source, and you can even set up your own proxy so you don't need to rely on gravitational's servers.
I guess it's not so much the posting of alternatives, but you're really selling that particular alternative. It'd be nice for Show HNs to be less cutthroat.
It does come of a bit like I'm selling it I guess, but I'm not affiliated. I'm all for alternatives and having a choice instead of a monopoly.
Like I said, this project looks great.
I also don't see anything in the guidelines about this kind of thing, has a mod commented about it before?
This wasn't a Show HN when the comment was posted, though, so it's a moot point.
This link is to https://github.com/spolu/warp?attempt=8. If one needs to add an "attempt" HTTP parameter to track submissions of the same URL, and this is the 8th attempt, that seems like way too many.
Here's a few prior identical submissions by the same person:
1: https://news.ycombinator.com/item?id=14398392 (ie, https://github.com/spolu/warp?attempt=1)
4: https://news.ycombinator.com/item?id=14407813
6: https://news.ycombinator.com/item?id=14452505
If 8 isn't too many, what is? 20? Submit the same link every day indefinitely until it reaches the front page?
Certainly, if someone persists in trying and the thing just never gets popular, that's just spam. But if "the right timing" was all that was needed to cause the sumission to hit #1? Maybe "the right timing" needs to be a concept built into the submission queue.
Most examples of this are one person submitting daily articles from their own site or sites they're paid to market. Sometimes even those end up near the top of the front page, and often when that happens, if one looks at prior submissions from that same person and site, the article that made the front page seems like it would do worse than prior articles.
I could see all of this as an indicator that the ranking/voting doesn't do a great job of letting interesting stuff get a shot, nor of penalizing folks who constantly submit posts on their own site (for months - different than this situation). The "New" page is easy enough to ignore that I could imagine few visitors looking at it regularly, so the profile of visitors to that page is different than to the home page.
Different titles he used, in chronological order:
* Show HN: Warp – Simple terminal sharing for better developers interactions
* Warp – share your terminal with one simple command
* Show HN: Instantaneous terminal sharing Instantaneous terminal sharing
My take away from this: Don't include app/product name, describe product in as few words as possible, don't include examples (... for ...) so readers has the opportunity to imagine the possibilities.
> Otherwise please use the original title, unless it is misleading or linkbait.
Basically, the HN title should be the page title (with a few exceptions noted in the doc above). The whole point is not to use the title to do what you're proposing and apparently, observing.
My interest wasn't "How do I get something to rank on HN?", it was "I want to encourage people to submit things that they discover and love, not repeatedly submitting things they're affiliated with." I may be in the minority, though.
* You don't need to rely or surrender to the cloud.
* Neither you nor the clients need to create an account (or worse, require a google/facebook account).
I would imagine that this goes through someone's server. It would be helpful if the readme gave a little more detail about how this works.
https://github.com/spolu/warp/blob/master/daemon/cmd/warpd/m...
Looking through the source code, I've found these lines:
https://github.com/spolu/warp/blob/master/client/command/con... https://github.com/spolu/warp/blob/master/client/command/con... https://github.com/spolu/warp/blob/master/protocol.go#L13
It looks like it defaults to connecting to `warp.link:4242`. I can't tell if it's routing the entire connection through warp.link or if it's just resolving the name to an IP address that then connect directly (I don't know Go very well).
Assuming no malicious intent, not disclosing anything about it in the readme suggests not very security oriented mindset and therefore it's likely just not secure enough to use.