kdeconnect-ios VS Mosh

Available for Linux, Windows, Android, IOS Since you're asking for IOS, here: https://github.com/KDE/kdeconnect-ios

GPL seems to be incompatible with the iOS store as that places some extra restrictions on it. [0] [1]. Some GPL apps such as KDE Connect have a special exception in their license for the ios App Store. [2]

[0] https://opensource.stackexchange.com/questions/9500/is-apple...

[1] https://news.ycombinator.com/item?id=12827624

[2] https://github.com/KDE/kdeconnect-ios/blob/master/License.md

They acknowledge the GPL conflict in [the license file](https://github.com/KDE/kdeconnect-ios/blob/master/License.md):

> …we have committed not to pursue any license violation that results solely from the conflict between the GNU GPLv3 and the Apple App Store terms of service, including the FOSS-specific policies as outlined in sections 3.3.22, 5.1, and 9.1

Fun fact KDE Connect is also available on iOS, so you can connect your android phone with an ipad or iphone with a window. The iOS version is still in beta though and a lot of features are still limited. https://github.com/KDE/kdeconnect-ios

I don't know anything, but a search yields this KDEConnect repo for iOS https://github.com/KDE/kdeconnect-ios

There is a beta version of KDE Connect on iOS you can get through TestFlight. It’s not fully featured due to the lack of background processing which means no notification sync and the app must be open to use it, but everything else should be working. I know file transfer and virtual touchpad work. https://github.com/KDE/kdeconnect-ios

KDE Connect for IOS is in public testing that you can try it. https://github.com/KDE/kdeconnect-ios

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.