tmate VS Neko

$ apt-cache show tmate [...] Homepage: http://tmate.io/ Description-en: terminal multiplexer with instant terminal sharing tmate provides an instant pairing solution, allowing you to share a terminal with one or several teammates. Together with a voice call, it's almost like pairing in person. The terminal sharing works by using SSH connections to backend servers maintained by tmate upstream developers; teammates need to be given a randomly-generated token to be able to join a session. . tmate is a modified version of tmux, and uses the same configurations such as keybindings, color schemes etc.

Checkout https://tmate.io/

https://tmate.io/ works for this scenario, even though it can create some issues with truecolor.

That exactly what tmate is made for

Well here's a similar project you can look at: https://github.com/nurdism/neko

Not sure how well it would work but there’s a thing called n.eko I’ve used in the past. It’s a docker container that hosts a web browser as a website that multiple people can go to and all watch the same screen. It has adjustable resolution too so you can pick whatever works for your bandwidth. While the original version does only support a web browser you can tweak the docker config to dump you to a Linux desktop instead where you could play it in your preferred watching software. One downside to this method is it needs 2 ports forwarded for every user in addition to the ports for the site itself. here’s the link

The best implementation I have seen of this is neko. The responsiveness is good enough for real-time IMO.

github Reddit post

Share browser with friends, watch movie, Shop or do whatever together

I saw also docker image for setting up a browser that will do a sharescreen but I never tested it yet (https://www.watchparty.me/) or (https://github.com/nurdism/neko).

Another way I have been doing it is using neko it is a web browser that outputs to RTMP. You could run this on a server and then join the conference call. It would load the page and get the usual conference experience. You could then send that to a RTMP server.

You could try n.eko.