• Sources: blinry.org, HN 49092112
  • Summary: A post on blinry.org reports three weeks of testing multi-seat setups on Wayland. The core Wayland protocol already binds every input event to a seat, and sway together with wayvnc supports transient seats end to end. The failures the author hits are in toolkits and applications, which assume one pointer and one keyboard.
  • Why it matters: It locates the blocker for multi-cursor collaboration in application and toolkit code rather than in the display stack, which changes who has to do the work.

send feedback on this story