If that is the case, then you can probably easily find the X server code in the Linux kernel and send a link? Spoiler: it is not there

Waypipe has nothing to do with the kernel mode setting driver. The X server code does not run in the kernel. Wayland compositors use kernel modesetting for mode changes, so not sure what your point is? Not saying you need to switch to Wayland, just saying that it covers the use case you described as impossible with Wayland.

@hummus273 Xvnc does not allow you to display individual applications only an entire desktop. I’m monitoring about 20 different computers doing different things and for me it is a significant advantage not to have to bring up a whole desktop but to be able to launch a single graphical application on my existing desktop.

Yes, that is what I meant with not as convenient.

I don’t really understand the degree of emotional attachment people have to one solution or another. For me it’s a simple application case, for me Wayland is not desirable, not only does it not network

Your use case is covered by waypipe (which in my tests is much more responsive than X11 forwarding).

the embedded X-server as part of the kernel works very effectively by avoiding the kernel/userland switches an ordinary X server would require.

I think you are confusing stuff here. Which kernel has an embedded X server?

So for my use case, Wayland is NOT a replacement and so I have to object to people arguing that it is a full replacement for X, it is not.

What part of your use case is not covered by waypipe?

Firefox is not a game?

You assume I’m not using it. On the contrary, I use it a lot at work. We have some old TK interfaces. They take ages to load over the network. The interfaces load much faster when using Xvnc running on the remote machine rather than X forwarding (but it is not as convenient).

Not having any lag is physically impossible. You don’t notice it maybe. But if I open Firefox with X forwarding on the same network (1gbe) it is very noticeable for me.

X’s network transparency is overrated IMHO. Since ages most data on desktops is sent via shared memory to the X server (MIT-SHM extension) otherwise the performance would suck. This does not work over the network and so X over the network is actually quite slow. Waypipe works way better for me than SSH X forwarding.

I’m sure he is joking. For example the lowest key size openssl supports is 512 bits and this is really small. Anything below 1024 bits has been considered insecure for a while now. Typical RSA key length is 2048. For a 22 bit RSA key you don’t need a quantum computer, this is so small a laptop CPU can break this in a short time. As with EC crypto: this won’t save you from quantum computer attacks, in fact a typical 256 bit EC key needs less qbits to be broken (1500) then 2048 bit RSA(4096).