4 ms·
WayPipe fulfills the same need and in a modern context there's really no advantage to the way X does it.
by AnIdiotOnTheNet 4y ago
WayPipe fulfills the same need and in a modern context there's really no advantage to the way X does it.
- GekkePrutser 4y agoCan it also stream single programs instead of whole desktops? As I understand it that was still something that wasn't possible. And it's exactly what I use all the time (windows from different systems on one desktop)
- AnIdiotOnTheNet 4y agoYes, that's it exactly its primary purpose: to replace X forwarding. > waypipe should be installed on both the local and remote computers. There is a user-friendly command line pattern which prefixes a call to ssh and automatically sets up a reverse tunnel for protocol data. For example, waypipe ssh user@theserver weston-terminal will run ssh, connect to theserver, and remotely run weston-terminal, using local and remote waypipe processes to synchronize the shared memory buffers used by Wayland clients between both computers.
- GekkePrutser 4y agoAha I have to look more into this, thanks. I can't currently use Wayland on most of my systems (it's broken for KDE on FreeBSD which I use the most) so I haven't really spent much time really looking into it. But this sounds interesting, I'm glad this usecase is finally being considered. 'shared memory buffers' sounds like an exploit waiting to happen though. Of course X11 is no better in this regard, an X-Client running on a remote X-Server has complete access to the remote display(s). But this is something that is unfortunately a design flaw from more naive times. And if there had been an X11R7 and onwards it would no doubt have addressed it. I think part of the problem here is that the same people promoting Wayland have also taken X11 on board to 'maintain' so they have all the incentive to let it die. I'd have preferred to see an organisation that was ready to take it into the future.