Wayland!

[brandon-northcutt]

Hi x2x team!

I've just discover x2x and I can see it being part of my daily use from now on. One problem that is looming on the horizon is the Wayland compositor which seems poised to replace Xorg. I'm using Fedora 25 now and it defaults to Wayland. x2x fails to work, but no error messages are thrown on either side of the connection. I suspect there is some deficit in Wayland's backwards compatibility features has failed to implement a necessary API interface for x2x.

My question is, can we modify x2x to also support Wayland? Should we make some API requests to the Wayland team? Should we do a refactor as part of the modernizing that has been requested on this project's README.md? I may have some programming time to spare. Let me know your thoughts on the correct path forward.

[brandon-northcutt]

P.S. for anyone wanting x2x to work in Fedora 25: Uncomment the WaylandEnable=false line in /etc/gdm/custom.conf and reboot. Then x2x will work fine.

[barak]

Wayland has security features which I suspect will make x2x very difficult to port.

[dottedmag]

Porting it to Wayland would be cool, though I believe one will have to throw away everything and start afresh. Not sure the result should be called x2x, but maybe w2w?

Anyway, the project is dormant, so if anyone wants to pick it up and turn it into a Wayland client I don't see any problem with that.

[andrew-aitchison]

x2vnc and win2vnc might also be useful comparisons.

I haven't seen a vnc2vnc but it could be instructive to hear about interest in w2w, x2w and w2vnc.

[andrew-aitchison]

I wonder whether waypipe solves the same security issues ?

[andrew-aitchison]

... and wayvnc is presumably relevant too ?

[andrew-aitchison]

... libei - the Emulated Input library might also help.

[dottedmag]

Please check out https://github.com/input-leap/input-leap