[nonethewiser]

SSHing into a terminal with your phone is terrible UX. Very low bandwidth. Voice input into a native app is not. We are not talking about fine grained control of your system by running explicit commands. We are talking about programming in plain English.

[advael]

I can use ssh as the transport and authentication layer over any internet connection through a fairly easily learnable set of ssh flags that can be further simplified through aliasing. As a bonus it's e2ee. The overhead from that affects latency but not bandwidth. Let's set aside ssh for a second. Streaming voice over the internet is a long-solved problem, I've been able to host a mumble server on a toaster since forever ago. So if the local machine can recognize voice commands, talking through a phone shouldn't make a difference. Like, if this works locally, and it works on the phone or whatever, why is having it talk over the internet the hard part? Whatever you think of the application itself, this is a weird failure mode