pwnagotchi VS Mosh

Merged and corrcted in jan could try that or as mentioned in another comment w solved this a while back in the forums remember to run the demo on your unit to verify what drivers it needs etc but it's been solved long ago https://github.com/evilsocket/pwnagotchi/issues/1134

yeah cause when you enable pwnagotchi to use pwngrid all you actually did was tell pwnagotchi to use api/pwnagotchi.ai which is down so your pwnagotchi will now try to connect to the internet, then it will try to send data to the API at pwnagotchi.ai and that API has been removed from the site. this is like telling the babysitter to call grandma but grandmas phone got cut off after a bad storm you can dial the number all day the wire to the house got cut there's no way for you to connect that way right now...

ok so all the Drivers for all the supported boards are added to the lib folder during build so if you add that stuff to the repo you download before you build it into an image. then adjust the display.py file to have a call back for your new drivers then you can set config to call up your screens drivers. After that you may need to adjust voice.py in order for screen element to display correctly based on your eink resolution.

Use the same config from pwnagotchi.ai but use this Image

1st Image used: https://github.com/evilsocket/pwnagotchi/releases/tag/v1.5.5

fatal: unable to access 'https://github.com/evilsocket/pwnagotchi.git/': Could not resolve host: github.com

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.