Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mosh: The Mobile Shell

mosh.org

Post reply on HN
Print view View original

151–158 of 158 posts

Re: Mosh: The Mobile Shell

#151

Post by hnrj95 »

keithwinstein wrote: post #43
shp0ngle wrote: post #4

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…

mosh has been a pleasure to use. thanks for all the hard work :). i think it’s worth experimenting with blink, too, if someone (like me) has the odd desire to try and be productive from an iphone or ipad

Re: Mosh: The Mobile Shell

#152

Post by buzzdenver »

eminence32 wrote: post #120
only_as_i_fall wrote: post #113

Earlier quoted context omitted.

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.

Is there anything preventing you from running the latest version from git? Is there something special about a "release" that you're looking for? (I can think of several reasons why someone might want a release and not the latest master branch, but I'm curious about your specific reasons)

I am not OP, but think of it from a contributor's point of view: you work X hours on a new feature that even gets accepted into the master, but then you know that 99.9% of mosh users will not see it because it's not part of a release. I don't know how I would feel about that.

Re: Mosh: The Mobile Shell

#153

Post by anthony_barker »

keithwinstein wrote: post #43
shp0ngle wrote: post #4

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…

I would love to use it more but:

1) Has there ever been a full security audit?

2) if not and I run it inside a VPN (wireguard) doesn't that remove most of the benefits?

Re: Mosh: The Mobile Shell

#154

Post by goodpoint »

WesolyKubeczek wrote: post #131
goodpoint wrote: post #110

Earlier quoted context omitted.

I would not call a working and usable piece of software "abandoned". We should call it "completed".

Maybe once the glaring bugs in it are fixed. The ones where half of my keyboard shortcuts were acting funny (something like https://github.com/mobile-shell/mosh/issues/1147 ), or garbage left from some other screens/commands ( https://github.com/mobile-shell/mosh/issues/1079 ). Midnight Commander is also being drawn in a jumpy way. Note that I'm not speaking about new emojis or some novel Unicode stuff, it's the same…

> Maybe once the glaring bugs in it are fixed.

Paintings, books, movies... are finished with the bugs in.

Vulnerabilities need rapid fixes.

Every other bugfix requires additional effort and comes with the risk of introducing vulnerabilities or other bugs.

At some point 99.9% of the users are happy and the benefit of fixing another bug becomes marginal.

Re: Mosh: The Mobile Shell

#155

Post by WesolyKubeczek »

goodpoint wrote: post #154
WesolyKubeczek wrote: post #131

Earlier quoted context omitted.

Maybe once the glaring bugs in it are fixed. The ones where half of my keyboard shortcuts were acting funny (something like https://github.com/mobile-shell/mosh/issues/1147 ), or garbage left from some other screens/commands ( https://github.com/mobile-shell/mosh/issues/1079 ). Midnight Commander is also being drawn in a jumpy way. Note that I'm not speaking about new emojis or some novel Unicode stuff, it's the same…

> Maybe once the glaring bugs in it are fixed. Paintings, books, movies... are finished with the bugs in. Vulnerabilities need rapid fixes. Every other bugfix requires additional effort and comes with the risk of introducing vulnerabilities or other bugs. At some point 99.9% of the users are happy and the benefit of fixing another bug becomes marginal.

A tool is a tool, not a work of art. Tools are supposed to be used. Therefore, flaws in them need to be fixed.

Re: Mosh: The Mobile Shell

#156

Post by fidelramos »

na85 wrote: post #26
themodelplumber wrote: post #22

Earlier quoted context omitted.

I'm curious, do you use any kind of terminal windowing, or what do you do about dividing up screen space / multitasking on your phone? This is one thing I really like on my laptop--multitasking with the side-by-side advantage, by keeping various windows visible at once, and using virtual workspaces with hotkeys assigned. Anyway, cool to read your endorsement.

I leave tmux running on my machines serverside, so it's a matter of: 1. Log in 2. $ tmux a 3. Continue where I left off. It's nice to have/annoying not to have more screen for doing real work. But if I'm traveling I'm not doing real work.

Pro tip: run ssh "tmux attach || tmux" to have SSH automatically attach to an existing tmux session, or start a new one if there is no session.

Re: Mosh: The Mobile Shell

#157

Post by atatatat »

anthony_barker wrote: post #153
keithwinstein wrote: post #43

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…

I would love to use it more but: 1) Has there ever been a full security audit? 2) if not and I run it inside a VPN (wireguard) doesn't that remove most of the benefits?

Less with Wireguard.

Re: Mosh: The Mobile Shell

#158

Post by gsich »

Shish2k wrote: post #141
gsich wrote: post #140

Earlier quoted context omitted.

What? Instead of ./command you type screen ./command.

Will `screen ./command` automatically and seamlessly reconnect my ssh session when I roam between different wifi networks? Or do I need to reconnect to ssh for myself, and then run a second command to reattach to the screen session?

The second.
Post reply on HN