> Haven't tried over the internet,

It works, the user experience however might not be great. Latency is your enemy, as are occasional drop-outs. For remote connections outside a LAN, naked X11 isn't recommended. NoMachine's NX (or the shrink wrapped X2Go) were better suited for such.

▲

jolmg 10 hours ago | parent [-]

Bit puzzling how one looks at guides for NoMachine's NX / FreeNX / X2Go and they're all about desktop sharing instead of simply remote X11 clients though X11 compression which is what NX was about. It seems the tunneling through NX's X11 compression is done through the bit obscure nxproxy.

▲

guenthert 10 hours ago | parent [-]

The proxy is needed for session management (specifically suspending sessions), no?

	▲	jolmg 10 hours ago \| parent [-]
		No... > nxproxy is a tool that allows one to tunnel X sessions through the NX compression library. nxproxy is a backend application utilized by various client application (Remmina, X2Go Client, PyHoca-Gui, Arctica Client, TheQVD Client, etc.). https://manpages.debian.org/trixie/nxproxy/nxproxy.1.en.html It's what implements the X11 compression tunneling. "X sessions" in this case seems to refer to "X11 connection sessions" rather than "desktop sessions". Checking https://en.wikipedia.org/wiki/NX_technology there's a diagram of how NX works. Both hosts have nxproxy for the compression tunneling, and the remote has nxagent which is basically like Xnest/Xephyr (which would do more of the "desktop session management" role). Things like X2Go and FreeNX seem to add ssh tunneling on top of that. The important bit for purposes of remote X11 clients over the internet seems to be nxproxy. Hope I'm right anyway. Kind of hate having to deal with windows inside desktops inside windows.