13:54 <romangg> autistic: For now I want to only know if there are other developers and projects interested in that. If yes, then we need to agree on the technology to use (Wayland protocols, D-Bus, other) and a configuration example we want to start with, for example input device configuration.

14:01 <ifreund> we've already kind of started with wlr-output-management-unstable-v1, which has been working quite well in various wlroots based compositors for a while

14:02 <ifreund> input management is probably a good step up in complexity though

14:02 <ifreund> anyhow, as the maintainer of river I'd definitely prefer to see this happen over wayland as opposed to dbus. River doesn't depend on dbus and I don't intend for it to ever do so

15:35 <romangg> ifreund: I agree that D-Bus alone would not cover all the ecosystem. For Wayland protocols the security question must be answered at some point. Another option would be a separate IPC system like whot did with libei.

15:42 <emersion> well… consider libei, then consider virtual-keyboard+virtual-pointer

15:42 <emersion> there's a difference in complexity