00:59 <Guest83> hey just wanted to say thank you to the maintainer and creator of river, it's really cool

09:23 <ifreund> :)

09:23 <ifreund> leon-p: heh, you triggered that?

09:26 <ifreund> I replied to some stuff on the lobsters thread but didn't really have any desire to engage jwz directly

09:28 <ifreund> As usual, he's right that the model he proposes would be more secure

09:29 <ifreund> that is, there's less code that must be correct to ensure security and that code can be better shared betweer compostiors as it would be in the display manager

09:30 <ifreund> I do think that that proposed architecture poses UX challenges that aren't an issue with ext-session-lock though, for example users wishing notifications or some desktop shell components to remain visible

09:30 <ifreund> or input methods for the password prompt

09:31 <ifreund> Assuming the compositor implemetation is high quality, I see no serious issues with ext-session-lock

09:32 <tiosgz> done some very basic check wrt #877 (wl-mirror crash) and it gets to a failed wlroots assertion: https://0x0.st/HpnX.log

09:32 <ifreund> interesting, not sure at a glance if that is a wlroots bug or a river bug

09:33 <tiosgz> only reproducible with hardware output and physically unplugging it (not wlr-randr or whatever), which makes sense given what's happening

09:38 <ifreund> OK, so I'm done with my bachelor's thesis now (acutually it's been a couple weeks but I needed time mostly away from tech for a bit) Here's my short term plans for river:

09:38 <ifreund> 1. merge as many PRs as are ready

09:39 <ifreund> 2. Finally fix the messed up and over engineered resizing code I added to try and make mpv behave

09:39 <ifreund> 3. Fix all other bugs, implement drawing tablet support

09:39 <ifreund> 4. release 0.3.0?

09:40 <ifreund> I'm also considering upgrading river's master branch to Zig 0.11 after I merge as many PRs as I can (to avoid conflicts)

09:41 <tiosgz> yay, congrats!

09:45 <ifreund> thanks!

10:28 <Cornelius-Figgle> is it possible to retrieve settings set by riverctl?

10:29 <Cornelius-Figgle> ie get what `riverctl background-color` is set to?

10:29 <leon-p> that is not possible

10:29 <Cornelius-Figgle> okay thanks

10:30 <leon-p> if this is important to you, you can make an issue on github and explain your use case

10:31 <leon-p> ifreund: yes, I optimistically pointed out that screen-savers are indeed possible

10:31 <leon-p> didn't help though that some gnome dev dropped in to argue against the session-lock protocol...

10:32 <ifreund> classic gnome

10:34 <leon-p> I think what saved it was some X user argueing in favour of unlock on crash

10:35 <leon-p> stuff like that is exactly why I left reddit and forums, but sometimes the urge to correct people is strong

10:40 <ifreund> yeah, I left reddit quite a while ago as well

13:03 <p00f> ifreund: which zig version do i compile with?

13:45 <ifreund> p00f: right now master branch uses 0

13:46 <ifreund> 0.10

13:46 <ifreund> I've got a next-zig branch which uses 0.11 which I will probably merge into master in the next week or so

15:36 <p00f> thanks

23:43 <NickH> IIRC (and I may not) I think the plan was to realease 0.3.0 with zig 0.10 and then soon after bump to 0.3.1 with zig 0.11. Is that correct or am I imagining things?

23:44 <NickH> I don't see any mention of the zig version on https://github.com/riverwm/river/issues/796