00:06 <snakedye> elshize: You can send simulate_user_activity user activity request

00:06 <snakedye> bruh

00:06 <snakedye> https://wayland.app/protocols/kde-idle#org_kde_kwin_idle_timeout:request:simulate_user_activity

00:45 <elshize> do any command line tools exist that could do this, or do you have to do this programmatically?

01:22 <snakedye> You'll have to write your own client

01:22 <snakedye> Fortunately the protocol is dead simple

01:23 <elshize> snakedye: thanks; I've never done anything wayland before, so I'll need to go through some examples, maybe I find some time over the weekend.

01:24 <snakedye> I already wrote one client for this protocol

01:24 <snakedye> https://github.com/snakedye/midle

01:25 <elshize> snakedye: thank you kindly, I'll give it a look

10:08 <ifreund> elshize, snakedye: support wor wlr-idle-inhibit is planned, nobody's gotten around to implementing it yet though

11:38 <elshize> ifreund: thanks. maybe I'll look into this one, might learn something. not sure if I can find the time in the comming weaks though.

12:23 <novakane> oh 700 stars, on the road to 1000 before 0.1 :P

12:26 <ifreund> lol

15:46 <snakedye> ifreund: I find it weird that idle inhibit is a different protocol from Kde's idle. Seems like useless fragmentation

18:38 <kennylevinsen> compositor local protocols aren't officially designed works. KDE's idle protocol is just whatever they needed at the time.

22:24 <ifreund> that, and the fact that they do different things