2022/05/15

2022-05-15 00:30:17 +0200chomwitt(~chomwitt@2a02:587:dc21:9e00:e28b:dfc7:bbce:95de) (Ping timeout: 248 seconds)
2022-05-15 01:19:16 +0200 <Hash> Why not use a new key.
2022-05-15 01:20:26 +0200 <geekosaur> because this one's already known and signed by a few haskell people
2022-05-15 01:21:04 +0200 <geekosaur> granting that some of those are expired or revoked; I need to clean my keyring at some point
2022-05-15 01:21:20 +0200 <Hash> *nod*
2022-05-15 04:03:16 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 248 seconds)
2022-05-15 04:05:41 +0200stackdroid18(14094@user/stackdroid) (Quit: Lost terminal)
2022-05-15 04:06:58 +0200abiss27(~abiss27@user/abiss) (Quit: hasta la vista... tchau!)
2022-05-15 04:07:50 +0200stackdroid18(14094@user/stackdroid)
2022-05-15 04:08:46 +0200stackdroid18(14094@user/stackdroid) (Client Quit)
2022-05-15 04:28:35 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-05-15 04:43:28 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat)
2022-05-15 04:45:57 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1)
2022-05-15 05:53:26 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Read error: Connection reset by peer)
2022-05-15 06:44:55 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-05-15 07:00:10 +0200Benzi-Junior(~BenziJuni@dsl-149-64-179.hive.is) (Ping timeout: 240 seconds)
2022-05-15 08:18:20 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Ping timeout: 260 seconds)
2022-05-15 08:28:42 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-05-15 08:52:24 +0200abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Read error: Connection reset by peer)
2022-05-15 10:35:16 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds)
2022-05-15 10:50:39 +0200steve_(~steve@ool-182c2b80.dyn.optonline.net)
2022-05-15 11:00:12 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2022-05-15 12:46:56 +0200chomwitt(~chomwitt@2a02:587:dc21:9e00:a5cf:4aa7:c02f:9451)
2022-05-15 13:54:50 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2022-05-15 13:57:19 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-05-15 14:19:32 +0200mc47(~mc47@xmonad/TheMC47)
2022-05-15 15:15:50 +0200chomwitt(~chomwitt@2a02:587:dc21:9e00:a5cf:4aa7:c02f:9451) (Ping timeout: 252 seconds)
2022-05-15 15:20:13 +0200Benzi-Junior(~BenziJuni@88-149-64-179.du.xdsl.is)
2022-05-15 16:15:29 +0200catern(~sbaugh@2604:2000:8fc0:b:a9c7:866a:bf36:3407)
2022-05-15 16:16:32 +0200 <catern> possibly not an xmonad question: is it possible to display the same workspace on two monitors (of the same size/resolution) at once?
2022-05-15 16:16:47 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2022-05-15 16:17:30 +0200 <catern> this question inspired by my frustration at action-at-a-distance when I switch to workspace 2 on display A when workspace 2 is already being displayed on B
2022-05-15 16:19:07 +0200 <liskin> action-at-a-distance can be solved by swapping greedyView for view, or the other way around
2022-05-15 16:19:31 +0200 <liskin> re displaying same workspace on two monitors, xrandr --same-as does that
2022-05-15 16:20:39 +0200 <liskin> but actually being able to switch workspaces independently and also having the option to see a workspace twice, then no, that's not possible with X11
2022-05-15 16:21:16 +0200 <liskin> it'd only be possible if we controlled the compositor (like we'd need to in Wayland-land), but we don't
2022-05-15 16:23:10 +0200 <catern> got it, thanks!
2022-05-15 16:23:53 +0200 <catern> (so I guess I have something to look forward to in Wayland...)
2022-05-15 16:24:18 +0200 <geekosaur> the compositor would have to support it
2022-05-15 16:24:37 +0200 <geekosaur> for that matter, if there were a compositor that supported it in X11, you could do it here
2022-05-15 16:25:05 +0200 <geekosaur> but without compositor support you can't display the same window in two places in either window system
2022-05-15 16:26:08 +0200 <liskin> yeah technically it can be done in both, it's just that in X11 nothing forces the WM to talk to the compositor directly, so compositors tend to be general and features like this don't get implemented
2022-05-15 16:26:33 +0200 <liskin> in Wayland you're more or less forced to have your own compositor, so you might as well add niche features like this
2022-05-15 16:26:35 +0200 <catern> ah, I see, I see
2022-05-15 16:26:52 +0200 <liskin> or, as it's currently the case, simply give up and not implement anything at all :-D
2022-05-15 16:27:10 +0200 <liskin> because it ends up being much more of a maintenance burden
2022-05-15 16:27:10 +0200 <catern> are there any tiling window managers that have an integrated compositor in X11? (besides I guess tiling extensions for gnome shell and maybe others) I guess those are the ones which might theoretically support this, but forcing the integration means it seems more likely to be supported in Wayland (as liskin said)
2022-05-15 16:27:43 +0200 <geekosaur> gnome and kde only, I think
2022-05-15 16:27:51 +0200 <liskin> never heard of anything like that
2022-05-15 16:27:55 +0200 <geekosaur> for a week there was xmoniz though :)
2022-05-15 16:32:09 +0200chomwitt(~chomwitt@2a02:587:dc21:9e00:5530:2656:4793:d635)
2022-05-15 17:29:56 +0200 <geekosaur> mm, git is happy with my signing setup but gpg is throwing errors apparently on some ancient keys in my pubring. really need to clean it (export, nuke, and re-import apparently)
2022-05-15 18:00:18 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2022-05-15 18:18:19 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-05-15 18:56:31 +0200 <liskin> git these days can sign commits using ssh-agent as well, btw
2022-05-15 18:56:43 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-05-15 18:57:27 +0200 <liskin> not sure if that's a good idea but gpg's UI/UX is so horrible that I haven't managed to learn it in 20 years :-(
2022-05-15 18:59:43 +0200 <geekosaur> I'm not impressed with what I'll need to do to clean the pubring, yeh
2022-05-15 19:00:05 +0200 <geekosaur> there's a reason I hadn't used my key since 2009ish
2022-05-15 19:05:29 +0200 <geekosaur> interesting btw, since I started digging for my old key after seeing a commit message from (I thought you? may have been Solid) about putting keys in MAINTAINERS.md, and a grouse that only one maintainer had registered a pubkey with github
2022-05-15 19:06:22 +0200 <geekosaur> while I was digging for the commits to revert to debug the WindowNavigation border issue
2022-05-15 19:09:48 +0200 <geekosaur> having looked at ssh signing, I guess I'll stick with pgp since it's already set up and verified in another repo
2022-05-15 19:10:01 +0200 <geekosaur> and I already uploaded my pubkey to github
2022-05-15 19:53:45 +0200abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)
2022-05-15 20:18:10 +0200abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 240 seconds)
2022-05-15 20:23:53 +0200 <liskin> I see
2022-05-15 20:24:11 +0200 <liskin> we don't really have a specific usecase for the gpg keys in MAINTAINERS.md
2022-05-15 20:24:56 +0200 <liskin> it's just that it could be useful if we need to exchange sensitive stuff or someone else needs to send sensitive stuff to us
2022-05-15 20:41:51 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-05-15 21:11:34 +0200stackdroid18(14094@user/stackdroid)
2022-05-15 22:10:59 +0200Stellacy[m](~stellacym@2001:470:69fc:105::2:c12)
2022-05-15 23:12:56 +0200abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)