Post #4171870
2026-07-28 17:30 UTC
This was the first time I looked deeper into Wayland actually *is*! At its heart, it’s a collection of protocols. I was really happy to find that the core "wayland" protocol (that graphical programs and the Wayland compositor use to talk to each other) has deeply integrated multi-seat support!
Which is an awesome basis! 5/5 stars! :D ★★★★★
But for multi-seat to work, it has to be supported throughout the stack. So how well do Wayland compositors actually use these concepts?
Replies (1)
-
@blinry@chaos.social 2026-07-28 17:35
Weston (the old reference implementation of a Wayland compositor managed by the @XOrgFoundation@floss.social) was the first compositor I realized had real multi-seat support! You can configure input devices to belong to different "seats" using udev rules (see the blog post for details on how to set that up), and that'll give you multiple mouse cursors with independent window interactions! If you assign keyboard to the seats, you can also *type* into different windows, which feels very cool!