TIL: You can really decrease the bandwidth of your SSH sessions by setting ObscureKeystrokeTiming no.
SSH has a feature where it will send a bunch of dud packets in the stream to make it harder for an attacker with TCP-level access to guess what you're typing just by watching the timing of your keystrokes. If you don't care, you can just tell it to stop sending the "chaff" packets.
I strongly suspect for most intranet use cases, this is fine.
Termora è un terminale moderno e multipiattaforma con client SSH integrato, gestione SFTP, plugin avanzati e supporto per Windows, macOS e Linux. #Software#Linux#SSH#Windows#Mac
#sixels do “compress” image data by its nature design, #libsixel is highly optimized, on the other side #kittyterminal protocol
Direct transmission (t=d): RGB/RGBA -> base64 … huge data transfer RGB/RGBA -> PNG -> base64 … better in size, significant overhead RGB/RGBA -> zlib compression -> base64 … also significant overhead RGB/RGBA -> PNG -> zlib compression -> base64 .. even bigger overhead
Simple file transmission (t=f) Client needs access to file … Forget about #ssh
Temporary file transmission (t=t) Client needs access to /tmp, /dev/shm … forget about ssh
Shared memory object (t=s) Client needs to have access to POSIX shared memory object/Windows named shared memory object … forget about ssh.
So yes, kitty is “superior” protocol with superior performance, except it works as “superior” only on localhost and event that is questionable at least in case of #brow6el (ok I acknowledge thats this is very specific “hack”)
#kittyterminal image protocol is literally unusable on #ssh, and thats the whole point of terminal apps. If we need something we need to improve the #sixels but let’s start with broader support and don’t excuse it is legacy bad protocol, because tbh it works really well even in Microsoft terminal.
@314rate Fun fact with #marks : if you edit a remote file from your local #vim#nvim instance and add a #mark, you can later jump to it and the editor will reopen the #ssh connexion for you.
** WARNING: connection is not using a post-quantum key exchange algorithm. ** This session may be vulnerable to "store now, decrypt later" attacks. ** The server may need to be upgraded. See https://openssh.com/pq.html