2026/04/29

2026-04-29 01:46:29 +0000RMSBach(~RMSBach@24.210.2.24) (Quit: ZNC 1.9.1 - https://znc.in)
2026-04-29 01:46:43 +0000RMSBach(~RMSBach@2603:6013:9b40:6f2::1040) RMSBach
2026-04-29 02:45:34 +0000coldpress(~coldpress@124.143.212.35.bc.googleusercontent.com) (Quit: ZNC 1.10.1 - https://znc.in)
2026-04-29 02:46:55 +0000coldpress(~coldpress@124.143.212.35.bc.googleusercontent.com) coldpress
2026-04-29 04:00:49 +0000haskellbridge(~hackager@96.28.224.214) (Read error: Connection reset by peer)
2026-04-29 04:01:10 +0000haskellbridge(~hackager@96.28.224.214) hackager
2026-04-29 04:02:36 +0000jaysson(~jay@user/jaysson) (Quit: WeeChat 4.9.0)
2026-04-29 04:44:06 +0000 <haskellbridge> <c​olonelpanic> wondering if the sort of obvious idea of trying to make xmonad talk to river is an idea that anyone else has considerd. i did see that this was created recently https://codeberg.org/andrea_rossato/hs-wayland-scanner I think there are a lot of different ways that this could be approached. Maybe this is less feasible than I'm imagining it to be, but i do wonder if we could fork the core xmonad repo and try to keep its api as...
2026-04-29 04:44:12 +0000 <haskellbridge> ... consistent as possible. i think it might be possible to preserve a substantial portion of xmonad contrib this way as well. Thoughts?
2026-04-29 04:49:21 +0000 <geekosaur> it was discussed here recently, in fact
2026-04-29 04:49:41 +0000 <geekosaur> (search for "river")
2026-04-29 04:50:20 +0000 <geekosaur> there should even be an image from a quick vibe-coded PoC by Solid
2026-04-29 04:50:53 +0000 <geekosaur> still needs someone to do the actual work, plus translating contrib over will be a rather large project