←back to thread

532 points tempaccount420 | 6 comments | | HN request time: 0s | source | bottom
Show context
psanford ◴[] No.45396774[source]
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.

replies(28): >>45396871 #>>45397296 #>>45397372 #>>45397399 #>>45397495 #>>45397597 #>>45397619 #>>45397679 #>>45397940 #>>45398115 #>>45398136 #>>45398508 #>>45398532 #>>45398631 #>>45398858 #>>45398975 #>>45399238 #>>45399719 #>>45399778 #>>45400311 #>>45400334 #>>45400419 #>>45400814 #>>45400881 #>>45401030 #>>45401354 #>>45404259 #>>45415504 #
1. zdw ◴[] No.45396871[source]
Same - this feels equivalent of some rando making a repo called "Windows 12" or "Linux 7".
replies(3): >>45397120 #>>45399472 #>>45399643 #
2. bravetraveler ◴[] No.45397120[source]
LDAP2 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

3. asveikau ◴[] No.45399472[source]
You mean like cryptocurrency bros naming something "web 3.0"?
4. teddyh ◴[] No.45399643[source]
C.f. “JSON5”.
replies(2): >>45400557 #>>45401631 #
5. Dylan16807 ◴[] No.45400557[source]
Eh. 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.
6. imoverclocked ◴[] No.45401631[source]
I think you meant to say, “YAML3”