It took me a minute to realize this, but HyperShell seems to be (or can be thought of as) a demo app for the (previously unknown to me) "hyper ecosystem"---Hyperswarm, Hypercore, Hyperdrive, etc: https://docs.holepunch.to/ . Perhaps an even tighter example than HyperShell is hyperbeam [1]: look at the usage section and API, and then note that it's all implemented in like 200 lines of code.
I'm no expert in this field, but this stuff looks like legos for cutting-edge P2P solutions. I think this is the coolest thing I've seen since Tailscale.
I wonder what thought process causes authors to go for name collision instead of something like p2pshell which is more descriptive and has zero google results... Neat tool, however.
I guess the lesson here is you don't have to use any of the technologies in the project as part of the project name if you don't want to. Especially if the namespace is already somewhat saturated. For my next project, TCPHTTPHTMLCSSJSLinuxAlpineContainerGCPGKEBlog...
Reread the thread starter. All those preexisting hyper things have nothing to do with this company, that's not the point.
And of course they're free to name their stuff after anything else they like, it's not a tricky question, it's just... weird? stupid? seo-manipulative? I don't know honestly, all I know is they had a more descriptive name at their disposal that had zero hits and they they passed on it.
I already said, they had a perfectly descriptive name but they chose the one easily confusable with 5 other things, I am curious to know their thought process. And what's yours?
Hyper is their protocol and I assumed they derived it from HTTP.
> Hypercore also includes a new URL scheme, hyper://, for referencing any Hypercore-based data structure. As Hypercores declare their data structure, this URL scheme can be used for a wide variety of use-cases. This URL scheme can improve interoperability among applications by providing flexible and modular access to hypercore directly.
All of their technology is based off of their hyper protocol.
But my point is that I don't really see the need to nazi people's nomenclature.
You could just, ya'know, discuss the tech itself...
> All of their technology is based off of their hyper protocol.
And that for some reason determines naming every product that uses that protocol.
> nazi
There's no need to be a nazi, but it should be an acceptable thing to ask, when identifier namespace is global, about why someone would choose to occupy an overlapping identifier even if a better more descriptive identifier is available, shouldn't it?
Also having a hard time groking it, but from the README looks like maybe the equivalent to setting up a TOR node to front an ssh daemon and routing a shell through the onion network to get to a host behind a NAT.
I'm thinking the same thing. Is there some kind of circumstance where I'd want to use this instead of SSH? I'm hardly inclined to fix what isn't broken at the best of times, but the p2p element just seems weirdly superfluous.
Accessing a “home computer” behind a NAT you don’t control or has a dynamic IP, eg. computers/devices that only have mobile connection and many (most?) broadband home connections.
I sometimes need to connect to a CI runner to debug some CI build script. I made a (quick hack of a) tool [0] for doing that by creating an Onion service on the runner listening to SSHD, and printing a one-liner I can paste on my dev machine to connect to it via Tor. This sounds like basically the same idea, but using a DHT and hole punching instead of onion routing.
Seems so: I like the idea. Would be, however, to integrate with mosh [1] and feel much better if there was a well audited SSH implementation beneath the hole punching and rendezvous layer.
How do you work in terminal having that hard pass feeling? There are numerous CLI utils written in scripting (usually interpreted) languages. They do their job so well that some of them are here for decades already. Actually quite a lot of people don't even realize that many of CLI things they use are shell, or Perl scripts.
I suppose it depends on what work someone is doing. I'm an SRE and haven't had too many issues keeping my CLI dependencies to a minimum. It could just be my minimalist nature creeping in, though.
I'm no expert in this field, but this stuff looks like legos for cutting-edge P2P solutions. I think this is the coolest thing I've seen since Tailscale.
[1]: https://github.com/mafintosh/hyperbeam