111–120 of 158 posts
This mimics a lot how 3270 devices work, by transmitting chunks instead of individual keystrokes. The IBM 3270 technology dates from 1970!
Sort of. Local echo and "smart current line editing" aren't quite the same as block mode, forms, etc. To me, a html form is closer to what 3270 is.
Earlier quoted context omitted.
If you have long running operations you can use screen/tmux.
You can use screen/tmux, but they’re both more complicated and less good when it comes to this specific use-case. Personally I use both - mosh (or et) for the seamless automatic-reconnect, and tmux as a console window-manager.
In what way are they more complicated? Granted screen is legacy, but tmux is just an executable on the server with sane defaults that Just Works OOTB.
Earlier quoted context omitted.
I think the truth is that we don't feel like we need a release. We've never had a security hole, our track record speaks for itself, and I wouldn't really want us to rush anything and blow that. There are some features that it would be really nice to have in a release (like 24-bit color support, and working around a recent MacOS clock bug), but I handed over the maintainership to somebody else about six years ago and…
Great response - not everything needs to be updated and upgraded every few days. Stability should be praised, not used as evidence of indolence.
Hiding behind "well we don't want to compromise the core software" after stringing other contributors along for years doesn't pass the sniff test.
Earlier quoted context omitted.
I think the truth is that we don't feel like we need a release. We've never had a security hole, our track record speaks for itself, and I wouldn't really want us to rush anything and blow that. There are some features that it would be really nice to have in a release (like 24-bit color support, and working around a recent MacOS clock bug), but I handed over the maintainership to somebody else about six years ago and…
> has never had a security hole -- we're pretty proud of that! With all due respect, you pride on this matter should be no bigger than your userbase is.
Mosh original author here -- fun to see us back here yet again. Happy to answer any questions.
It looks like there's no sponsorship for Mosh. Had this been considered? Not saying money would solve the challenges the maintainer faces but there might be things it eases. With a tool this popular I expect it wouldn't struggle to raise a fair bit.
Earlier quoted context omitted.
The title “Mosh: SSH for 2012” is amusing because now in 2021, ssh is still king.
In general, I prefer SSH when using reliable, low-latency links, mainly because of the various forwarding capabilities (agent, X11, ports), and sometimes because I need my output to be sequential. But for any kind of situation where the link might be dodgy, mosh is king.
Note that Mosh has not had release for 4 years, even when pull requests are accepted on github, and the team lead says "we are too busy/burned out". https://github.com/mobile-shell/mosh/issues/1115
i didn't know that, and that bums me out. is what's there good enough to not care that there aren't frequent updates?
Note that Mosh has not had release for 4 years, even when pull requests are accepted on github, and the team lead says "we are too busy/burned out". https://github.com/mobile-shell/mosh/issues/1115
I think the truth is that we don't feel like we need a release. We've never had a security hole, our track record speaks for itself, and I wouldn't really want us to rush anything and blow that. There are some features that it would be really nice to have in a release (like 24-bit color support, and working around a recent MacOS clock bug), but I handed over the maintainership to somebody else about six years ago and…
The difference that I think makes this comparison invalid is that Mosh is a communication tool, whereas Tex is running locally on files. We (as a community) have learned that any software with a networked attack surface slowly gets less secure over time - you (almost always) need to provide ongoing security fixes to maintain the desired level of security.
To be clear - I'm not saying you're wrong. I'm an intermittent user of Mosh and I can believe that no holes have been found that need patching (and that the team would in short order if necessary). It is, however, a signal that users of software look for. I like the idea in a sibling comment of the "documentation" commit just saying "we're still here" to reassure people.
Earlier quoted context omitted.
Great response - not everything needs to be updated and upgraded every few days. Stability should be praised, not used as evidence of indolence.
Except that it's a lie. Not accepting new feature requests is one thing, but what actually seems to be happening is that new code has been accepted into the master which then never sees the light of day. Hiding behind "well we don't want to compromise the core software" after stringing other contributors along for years doesn't pass the sniff test.