|
Top-level
@dickon @marcan Nothing written after the XRender extension (2000) uses network transparency on X11. It's all client-side buffers sent as images over the wire—something the X11 core protocol is *shockingly* bad at doing, because it interleaves commands and buffers, and that prevents even the simplest form of compression. Even VNC is more efficient. If you want remoting with Wayland, I strongly encourage you to look at RDP. 5 comments
 @_hic_haec_hoc @ebassi @marcan Most people don't care whether network transparency exists at all. People whose workflow includes remote devices mostly use pure ssh or locally running software accessing remote files or software with a proper client / server split. People who genuinely use it are a tiny niche and for basically all those use cases X network transparency is a hack in the first place. It is quite telling that no one cared about network transparency when designing Wayland. @ebassi @dickon @marcan @fenruspdx @ebassi @dickon @marcan Anyone sending RDP connections across the network without a VPN or SSH tunnel is asking for problems. You don't need to flag RC4, just use sensible tunnels for what they are designed for... securing network traffic. @winterschon I'll buy the "it should wrap in SSL by default' as solution.. I hope all the linux stack for this does that by default... I don't buy the VPN argument; that's not reasonable in practice. |
Gregory's Server
@ebassi @dickon @marcan I think that most people don't really care whether there's real network transparency or not, they just want to type "ssh -Y host", launch a GUI application and see it pop up on their screen. It looks like waypipe could provide this kind of experience but I haven't tried it yet so I don't know if it's full of papercuts