Implement native Wayland support for the Linux client
Current client runs through XWayland meaning you build it as an X11-based application.
While X11 has served Linux well for decades, it has limitations in terms of performance, security, and modern use cases.
Wayland is being adopted as the default display server in many major Linux distributions and desktop environments (e.g., GNOME, KDE Plasma). For example, distributions like Fedora and Ubuntu are pushing Wayland as the default, and more compositors (like Sway, Weston, and Mutter) are becoming Wayland-only.
Wayland is designed with better security in mind. X11 has a history of serious security flaws, including arbitrary access to windows and input events from other apps. In Wayland, each application is isolated and doesn't have access to other windows unless explicitly granted (via protocols like the "clipboard" protocol), which reduces the potential attack surface.
While XWayland provides backward compatibility for running X11 apps, it's a layer on top of Wayland that introduces additional complexity and performance overhead. Relying on XWayland means your app is not truly taking advantage of Wayland's features, potentially leaving you with a suboptimal user experience.
Embracing Wayland now will help you build better, faster, and more secure applications that will be ready for the future of Linux desktop environments.
