[Suggestion/Feature Request] Consider whether to expose window events on Wayland

[skewballfox]

This isn't exactly a feature request because whether or not this should be supported is probably something that is debatable. There is a legitimate use case for an application having access to window events, such as what window is in focus, where windows are being rendered, whether the user is currently inactive, etc. To give an example of an app that currently makes use of this data check out activity watch, ( I also recommend checking out the issue on wayland support, and the SO post linked from the FAQ.

here are a few relevant protocols, most are linked somewhere in the two recommeded pages above:

• wlr-foreign-toplevel-management
• kde-idle

[Drakulix]

Access to similar protocols will most likely be severely restricted in cosmic by default due to security concerns.

But we plan to support protocols similar to the ones linked. We are working with upstream to standardize these protocols.

• ext-foreign-toplevel-list was just merged
• ext-foreign-toplevel-state is being worked on
• and afterwards ext-foreign-toplevel-management can hopefully follow soon.

Additionally we plan to support the

• ext-idle-notify protocol
• ext-idle-inhibit protocols

We are using these protocols ourselves internally in our desktop environment, so support in general is not in question, but most of those will require some sort of privileged access due to the nature of information exposed here.
As far as I understand your use case, collecting sensitive information is very much the goal and I hope we can provide some way for users to explicitly allow such access for selected programs.

The story of authentication on the wayland-protocol layer is sadly not very well defined. So please understand, that while we view such a feature as desirable and the use-case to be perfectly valid, it is not the highest priority to sort out these things right now and a proper solution will likely take some time.

[skewballfox]

I'm glad to hear that

The story of authentication on the wayland-protocol layer is sadly not very well defined. So please understand, that while we view such a feature as desirable and the use-case to be perfectly valid, it is not the highest priority to sort out these things right now and a proper solution will likely take some time.

no worries, it's definitely one of those things that is best done perfectly or not at all. Let's face it, if you take explicit user opt in out of the equation it is spyware. but, in my view, the potential positive value in enabling this type of application is pretty immense. to give an example: time restrictions on specific applications, for those of us with executive function issues.