Hi Mobydeck, I've been using atch and ended up building two larger features on a fork (bash-tilde/atch (https://github.com/bash-tilde/atch)):
- Local session sharing — share/join/unshare, with SO_PEERCRED-based guest auth and read-only guests.
- Remote sessions — remote that bootstraps atch over SSH (host-key pinning, cross-arch binary staging, multiplexed auth).
- a musl static-build target reducing size to 105KB
I'd love to upstream whatever's useful, but I don't want to drop a 2,600-line PR on you. Are either of these in scope for atch? If so, I'm happy to split them into small, independently reviewable PRs in whatever order suits you or keep them on the fork if you'd rather atch stay lean. Either answer is totally fine.
Hi Mobydeck, I've been using atch and ended up building two larger features on a fork (bash-tilde/atch (https://github.com/bash-tilde/atch)):
I'd love to upstream whatever's useful, but I don't want to drop a 2,600-line PR on you. Are either of these in scope for atch? If so, I'm happy to split them into small, independently reviewable PRs in whatever order suits you or keep them on the fork if you'd rather atch stay lean. Either answer is totally fine.