8 ms·
I do hate the name ssh3. I was glad to see this at the top of the repo: > SSH3 is probably going to change its name. It is still the SSH Connection Protocol (R
by psanford 1y ago
I do hate the name ssh3. I was glad to see this at the top of the repo:
> SSH3 is probably going to change its name. It is still the SSH Connection Protocol (RFC4254) running on top of HTTP/3 Extended connect, but the required changes are heavy and too distant from the philosophy of popular SSH implementations to be considered for integration. The specification draft has already been renamed ("Remote Terminals over HTTP/3"), but we need some time to come up with a nice permanent name.
- cozzyd 1y agoSecure Hypertext Interactive TTY
- _joel 1y agoThat sounds a bit crap
- pixl97 1y agoHITTY then.
- BobbyTables2 1y agoBut this SHIT is really fast! You’ll see when the logs drop!
- zdw 1y agoSame - this feels equivalent of some rando making a repo called "Windows 12" or "Linux 7".
- bravetraveler 1y agoLDAP2 or nextVFS... but point awarded. Feels that way because it is. Though my examples aren't great. These things just are; not really versioned. I don't know if major differences would call for ++ A better 'working name' would be something like sshttp3, lol. Obviously not the successor to SSH2
- asveikau 1y agoYou mean like cryptocurrency bros naming something "web 3.0"?
- teddyh 1y agoC.f. “JSON5”.
- Dylan16807 1y agoEh. JSON forfeited version numbers, and if this analogy ran all the way through then we'd be looking at a scenario where SSH is based on HTTP 1 or 2. In that situation calling the HTTP/3 version SSH3 would make a lot of sense.
- imoverclocked 1y agoI think you meant to say, “YAML3”
- formerly_proven 1y agoEasy: hhs instead of ssh (since the even more obvious shh is essentially impossible to google). Stands for, idk, HTTP/3 Hardened Shell or something ("host shell"? sounds like windows)
- catlifeonmars 1y agohss? Http/3 Secure Shell?
- treve 1y agoOr h3ss, pronounced hess
- moralestapia 1y agoDon't use it! Create your own thing and name it however you want. Non-doers are the bottom rung of the ladder, don't ever forget that :).
- literalAardvark 1y agoNo... They're one rung up from evil and dumb doers.
- theandrewbailey 1y agoMaybe SSH/3 instead (SSH + HTTP/3)?
- techscruggs 1y agoI like this idea! Having SSH in the name helps developers quickly understand the problem domain it improves upon.
- bingabingabinga 1y ago[dead]
- throwaway127482 1y agoDoesn't /3 mean v3? I mean, for HTTP itself, doesn't the HTTP/3 == HTTPv3? If so, I don't see how this is any better than SSH3 - both SSH3 and SSH/3 read to me like "SSH v3"
- theandrewbailey 1y agoYes, but HTTP is about the only thing that versions with a slash. By writing it SSH/3, it would emphasize its relationship with HTTP/3, instead of it being the third version of SSH.
- deleted 1y ago[deleted]
- Dylan16807 1y ago> Doesn't /3 mean v3? I've seen very little do that. Probably just HTTP, and it's using a slash specifically to emphasize a big change.
- guerrilla 1y agoYeah, that's not cool.
- noman-land 1y agoSSHTTP
- zaik 1y agoHTTPSS for more confusion
- throwaway127482 1y agoSecureHyperTextShell (SHTS) I meant this in jest but now that I think about it, it actually could be a decent name (?)
- deleted 1y ago[deleted]
- BrightOne 1y agoI think it's too similar to HSTS: https://en.m.wikipedia.org/wiki/HTTP_Strict_Transport_Security https://en.m.wikipedia.org/wiki/HTTP_Strict_Transport_Securi...
- speed_spread 1y agoQUICSH/T
- irq-1 1y agoHyper Secure Shell (HSS)
- imoverclocked 1y agoYou could say it was just for SHTS and giggles?
- oofbey 1y agoSSHTTP3
- IgorPartola 1y ago
- ok123456 1y agoSSH over 3: SO(3). Like the rotation group.
- p1mrx 1y agoSSHoH
- Titan2189 1y agoSSHoH3 Pronounced "Shoe"
- CharlesW 1y agoh3sh | hush3 | qs | qsh | shh | shh3
- diego_sandoval 1y agoSSHoHTTP3
- thayne 1y agoqrs for Quic Remote Shell? Or h3s for HTTP 3 Shell? H3rs for http3 remote shell?
- ape4 1y agoHow about Tortoise Shell - a little joke because its so fast
- piannucci 1y agoHow about rthym or some variation?
- NewJazz 1y agohttps://github.com/francoismichel/ssh3/issues/79#issuecomment-1875615129 https://github.com/francoismichel/ssh3/issues/79#issuecommen...
- pdmccormick 1y agoHTTPSSH. Why not just SSH/QUIC, what does the HTTP/3 layer add that QUIC doesn’t already have?
- gclawes 1y agoThe ability to use HTTP authentication methods, HTTP headers, etc?
- arka2147483647 1y agoQuickShell - it should be called
- jacooper 1y agoQuicshell*
- bscphil 1y agoQSH?
- BobbyTables2 1y agoAt least that isn’t an existing ham radio Q-code!
- cpuguy83 1y agoThat's already a project (library for building a desktop environment).
- deleted 1y ago[deleted]
- ranger_danger 1y agoeasy access to reverse proxies
- attentive 1y agoussh (for udp)
- KronisLV 1y agoSSH/HTTP/3 That way, when you need to use sed for editing text containing it, your pattern can be more interesting: sed 's/SSH\/HTTP\/3/SSH over HTTP\/3/g'
- Wicher 1y agotry: sed 's:SSH/HTTP/3:SSH over HTTP/3:g' At least with GNU sed, you can use different separators so dodge the need for exscaping. | works as well.
- deleted 1y ago[deleted]
- 0x6c6f6c 1y agoSSH over QUIC so, maybe SSHoQ or SoQ soq reads better for the CLI I suppose.
- paulryanrogers 1y agoHTTP3 Shell or H3S
- unclet 1y agoWhy not HSH, or HTTPS Shell.
- nine_k 1y agoSSH2/3, maybe? It's still largely SSH2, but runs on top of HTTP/3.
- nine_k 1y ago/* This is one proper bikeshedding thread if I ever saw one. */
- dpflan 1y agosshhh ... don't sidetrack the productive comment generation. (also, SSHHH as a possible name)...
- akdor1154 1y agoQuissh?
- deleted 1y ago[deleted]
- manwe150 1y agoHow about ush then? The predecessor was rsh, and the next letter tsh is already taken
- BobbyTables2 1y agoush — “You shell” — Brilliant!
- BobbyTables2 1y agoRTH3EC is a certainly a mouthful…
- fsckboy 1y agomy autism plays out also in the world of words, i.e. names of things, and my comment here is more a reply to all my surrounding comments than to yours: ssh is not a shell and ssh is not a terminal, so please everybody stop suggesting name improvements that more deeply embed that confusion. back in the day, we had actual terminals, and running inside was our shell which was sh. then there was also csh. then there was the idea of "remote" so rsh from your $SHELL would give you a remote $SHELL on another machine. rsh was not a shell, and it was not a terminal. There were a whole bunch of r- prefixed commands, it was a family, and nobody was confused, these tools were not the thing after the r-, these tools were just the r- part. then it was realized that open protocols were too insecure so all of the r- remote tools became s- secure remote tools. http is a network protocol that enables other things and gets updated from time to time, and it is not html or css, or javascript; so is ssh a network protocol, and as I said, not a shell and not a terminal. just try to keep it in mind when thinking of new names for new variants. and if somebody wants to reply that tcp/ip is actually the network protocol, that's great, more clarification is always good, just don't lose sight of the ball.
- e12e 1y agoQuickshell/qsh?