IRCBrowse

2021/11/01

2021-11-01 00:07:31 +0100humky_(~humky@user/humky) (Quit: Leaving)
2021-11-01 00:09:16 +0100gruntsplatter(~sogens@gateway/vpn/pia/sogens)
2021-11-01 00:12:49 +0100seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-11-01 00:15:02 +0100geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-11-01 00:15:22 +0100geekosaur(~geekosaur@xmonad/geekosaur)
2021-11-01 01:33:59 +0100alternateved(~user@staticline-31-183-149-3.toya.net.pl) (Ping timeout: 264 seconds)
2021-11-01 01:46:46 +0100electr0n(~electr0n@about/security/founder/electr0n)
2021-11-01 02:00:21 +0100humky(~humky@user/humky)
2021-11-01 02:33:10 +0100trillp(~trillp@69.233.98.238)
2021-11-01 02:41:42 +0100Extropy(~extropy@gateway/tor-sasl/extropy) (Ping timeout: 276 seconds)
2021-11-01 02:44:34 +0100Extropy(~extropy@gateway/tor-sasl/extropy)
2021-11-01 02:45:30 +0100 <FOSSHuman[m]> Hello everyone. I have been using X.A.UpdatePointer, and since I have it set to move the mouse pointer to the exact bottom right of every window; When a floating window pops up, the pointer cannot "escape" the floating window, it is fine with normal tiled windows, but the fact that the pointer feels constrained to within the floating window, it makes the experience strange and feel constricting (like: I HAVE to do the thing in this
2021-11-01 02:45:30 +0100 <FOSSHuman[m]> dialogue RIGHT NOW), anyone suggest a fix to this??
2021-11-01 02:46:34 +0100 <FOSSHuman[m]> * in this floating dialogue RIGHT
2021-11-01 02:48:06 +0100 <FOSSHuman[m]> But I guess it does help with focus lol, to stop me from procrastinating and looking at reddit/HN while an important floating dialogue pops up lol...
2021-11-01 02:49:32 +0100 <FOSSHuman[m]> TLDR: X.A.UpdatePointer does not allow the pointer to "escape" certain floating dialogues.
2021-11-01 02:52:07 +0100 <FOSSHuman[m]> I have commented out X.A.UpdatePointer for the meantime, and I'm just using the default XMonad mouse window focus behaviour..
2021-11-01 02:53:51 +0100mvk(~mvk@2607:fea8:5cc1:300::d3fb) (Ping timeout: 245 seconds)
2021-11-01 02:56:25 +0100catman(~catman@user/catman) (Read error: Connection reset by peer)
2021-11-01 02:56:27 +0100 <FOSSHuman[m]> > `TLDR: X.A.UpdatePointer does not allow the pointer to "escape" certain floating dialogues.` The pointer just returns to the coordinates (in my case, the bottom right of the window)...
2021-11-01 02:56:29 +0100 <lambdabot> <hint>:1:1: error: parse error on input ‘`’
2021-11-01 03:04:40 +0100ArgoLargo[m](~argolargo@2001:470:69fc:105::1:16b1) ()
2021-11-01 03:09:06 +0100catman(~catman@user/catman)
2021-11-01 03:19:42 +0100mvk(~mvk@2607:fea8:5cc1:300::d3fb)
2021-11-01 03:47:44 +0100mvk(~mvk@2607:fea8:5cc1:300::d3fb) (Quit: Konversation terminated!)
2021-11-01 03:47:47 +0100Hash(~stoned@is.coding.when.stoned.io) (Ping timeout: 264 seconds)
2021-11-01 04:04:22 +0100banc-(banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds)
2021-11-01 04:24:10 +0100banc(banc@gateway/vpn/airvpn/banc)
2021-11-01 04:26:27 +0100catman(~catman@user/catman) (Read error: Connection reset by peer)
2021-11-01 04:47:18 +0100thunderrd(~thunderrd@183.182.110.1) (Ping timeout: 260 seconds)
2021-11-01 04:49:02 +0100catman(~catman@user/catman)
2021-11-01 04:52:40 +0100Extropy(~extropy@gateway/tor-sasl/extropy) (Quit: WeeChat 3.3)
2021-11-01 04:54:43 +0100Hash(~stoned@is.coding.when.stoned.io)
2021-11-01 05:03:57 +0100darkstarx(~darkstard@2601:1c2:300:c8a0::6c32) (Quit: Leaving)
2021-11-01 05:11:59 +0100darkstardevx(~darkstard@2601:1c2:300:c8a0::6c32)
2021-11-01 05:13:49 +0100darkstardevx(~darkstard@2601:1c2:300:c8a0::6c32) (Remote host closed the connection)
2021-11-01 05:14:14 +0100darkstardevx(~darkstard@2601:1c2:300:c8a0::6c32)
2021-11-01 05:16:39 +0100trillp(~trillp@69.233.98.238) (Quit: nyaa~)
2021-11-01 05:35:03 +0100trillp(~trillp@69.233.98.238)
2021-11-01 05:40:54 +0100gruntsplatter(~sogens@gateway/vpn/pia/sogens) (Ping timeout: 260 seconds)
2021-11-01 06:54:12 +0100berberman(~berberman@user/berberman) (*.net *.split)
2021-11-01 06:54:13 +0100Eoco(~ian@x-160-94-179-157.acm.umn.edu) (*.net *.split)
2021-11-01 06:54:13 +0100haskl(~haskl@user/haskl) (*.net *.split)
2021-11-01 06:54:13 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (*.net *.split)
2021-11-01 06:54:13 +0100incertia(~incertia@d4-50-26-103.nap.wideopenwest.com) (*.net *.split)
2021-11-01 06:54:45 +0100Eoco(~ian@x-160-94-179-157.acm.umn.edu)
2021-11-01 06:55:42 +0100haskl(~haskl@user/haskl)
2021-11-01 06:55:50 +0100incertia(~incertia@d4-50-26-103.nap.wideopenwest.com)
2021-11-01 06:55:55 +0100berberman(~berberman@user/berberman)
2021-11-01 06:57:57 +0100kr1x(~kriket@170.249.0.122)
2021-11-01 06:59:57 +0100thunderrd(~thunderrd@183.182.110.1)
2021-11-01 07:02:50 +0100Solid[m](~slot-matr@2001:470:69fc:105::1:a84) (*.net *.split)
2021-11-01 07:02:50 +0100lisq(~quassel@lis.moe) (*.net *.split)
2021-11-01 07:02:50 +0100Arcanus[m](~archanusm@2001:470:69fc:105::f953) (*.net *.split)
2021-11-01 07:02:50 +0100diaspora[m](~diasporae@2001:470:69fc:105::93e) (*.net *.split)
2021-11-01 07:02:50 +0100Industrial[m](~industria@2001:470:69fc:105::eb9) (*.net *.split)
2021-11-01 07:02:50 +0100unclechu(~unclechu@2001:470:69fc:105::354) (*.net *.split)
2021-11-01 07:02:50 +0100denbrahe[m](~denbrahem@2001:470:69fc:105::19c0) (*.net *.split)
2021-11-01 07:02:51 +0100dexterfoo(dexter@2a01:7e00::f03c:91ff:fe86:59ec) (*.net *.split)
2021-11-01 07:03:04 +0100lisq(~quassel@lis.moe)
2021-11-01 07:03:43 +0100dexterfoo(dexter@2a01:7e00::f03c:91ff:fe86:59ec)
2021-11-01 07:05:47 +0100diaspora[m](~diasporae@2001:470:69fc:105::93e)
2021-11-01 07:09:33 +0100unclechu(~unclechu@2001:470:69fc:105::354)
2021-11-01 07:10:49 +0100Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2021-11-01 07:10:53 +0100denbrahe[m](~denbrahem@2001:470:69fc:105::19c0)
2021-11-01 07:10:55 +0100gruntsplatter(~sogens@gateway/vpn/pia/sogens)
2021-11-01 07:11:42 +0100Industrial[m](~industria@2001:470:69fc:105::eb9)
2021-11-01 07:11:43 +0100Arcanus[m](~archanusm@2001:470:69fc:105::f953)
2021-11-01 08:52:15 +0100 <Solid> instead of a logHook, you could try adding updatePointer to all keybindings where that makes sense
2021-11-01 08:52:23 +0100 <Solid> like changing focus/screens and the like
2021-11-01 08:52:50 +0100 <Solid> this should make it more predictable and less susceptible to weird behaviour like that
2021-11-01 09:17:27 +0100geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-11-01 09:17:51 +0100geekosaur(~geekosaur@xmonad/geekosaur)
2021-11-01 09:29:23 +0100mc47(~mc47@xmonad/TheMC47)
2021-11-01 09:32:12 +0100cfricke(~cfricke@user/cfricke)
2021-11-01 09:33:20 +0100qbt(~qbt@user/edun)
2021-11-01 09:33:24 +0100gehmehgeh(~user@user/gehmehgeh)
2021-11-01 09:53:23 +0100tremon(~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl)
2021-11-01 10:07:44 +0100L29Ah(~L29Ah@wikipedia/L29Ah)
2021-11-01 10:21:48 +0100 <gehmehgeh> L29Ah: hello
2021-11-01 10:22:47 +0100 <gehmehgeh> L29Ah: Btw. I tried your picom settings, which worked dealt with the tearing, but introduced a weird bug where xmonad window frames would turn on and off, if you will, (focused window, unfocued window, by colour) sometimes when I type in them
2021-11-01 10:22:47 +0100 <gehmehgeh> and sometimes not
2021-11-01 10:23:40 +0100 <gehmehgeh> uhm, I'm still not entirely awake. I hope that sentence made sense :)
2021-11-01 10:23:42 +0100 <L29Ah> you can try dropping some of the options
2021-11-01 10:23:54 +0100 <L29Ah> it's magic that i came with after reading the man page and trying
2021-11-01 10:23:54 +0100 <L29Ah> i
2021-11-01 10:24:01 +0100 <L29Ah> 'm on UHD630 so YMMV
2021-11-01 10:24:48 +0100 <liskin> gehmehgeh: borders on and off is the damage option
2021-11-01 10:25:01 +0100 <gehmehgeh> liskin: really? ok
2021-11-01 10:25:09 +0100 <liskin> Known bug, nobody knows if it's in picom or Xorg
2021-11-01 10:25:39 +0100 <gehmehgeh> ah, thanks for the info, liskin :)
2021-11-01 10:26:40 +0100 <L29Ah> worksforme
2021-11-01 10:27:20 +0100 <L29Ah> a worse thing is that it's slow with Tabbed, had to bisect and patch it
2021-11-01 10:27:52 +0100 <gehmehgeh> L29Ah: have you upstreamed said patch?
2021-11-01 10:28:17 +0100 <L29Ah> almost: https://github.com/yshui/picom/issues/381#issuecomment-949279059
2021-11-01 10:28:28 +0100 <L29Ah> you just revert one of these :)
2021-11-01 10:30:54 +0100 <liskin> I wonder just how slow picom is these days. I'm still on compton :-)
2021-11-01 10:32:40 +0100 <L29Ah> it's same as compton with these reverted afair
2021-11-01 10:34:11 +0100 <liskin> Oh, right, those patches are quite old indeed
2021-11-01 10:34:19 +0100 <liskin> Might give it a try :-)
2021-11-01 11:03:57 +0100 <FOSSHuman[m]> Sol : id Thanks for the suggestion.. I have tried to combine both a `Navigate` type function such as `Go :: Direction2d` and an `X` type function such as `updatePointer` and, when recompiling XMonad, GHC returns the error message of it being the wrong type (recalling from memory, not on PC rn), how would I do what you suggested, any way to combine 2 functions of different types in an `additionalKeysP` keybind?? Please forgive me not
2021-11-01 11:03:57 +0100 <FOSSHuman[m]> knowing too much about this, this might be a dumb question...
2021-11-01 11:04:11 +0100 <FOSSHuman[m]> s/Sol/@Solid/, s/: id//
2021-11-01 11:25:39 +0100 <Solid> FOSSHuman[m]: perhaps post the code once you're back at a computer; then I'll try to guide you through it
2021-11-01 11:26:17 +0100 <FOSSHuman[m]> Ok, no problem
2021-11-01 13:16:37 +0100 <FOSSHuman[m]> I have tried to do a keybind like: `("M1-<L>", sendMessage $ Go L >> updatePointer (0.95, 0.95) (0, 0))` but GHC throws out an error saying it's the wrong type??
2021-11-01 13:18:07 +0100 <FOSSHuman[m]> `Couldn't match expected type ‘X a0’ with actual type ‘Navigate’`
2021-11-01 13:18:17 +0100 <FOSSHuman[m]> `In the first argument of ‘(>>)’, namely ‘Go L’`
2021-11-01 13:18:42 +0100 <FOSSHuman[m]> `In the second argument of ‘($)’, namely
2021-11-01 13:18:42 +0100 <FOSSHuman[m]> ‘Go L >> updatePointer (0.95, 0.95) (0, 0)’`
2021-11-01 13:19:29 +0100 <FOSSHuman[m]> How do I combine two functions with different types in this case?
2021-11-01 13:20:19 +0100 <fizzie> I would guess the problem there is the very low precedence of $ rather than types per se.
2021-11-01 13:21:08 +0100 <fizzie> Try `(sendMessage $ Go L) >> updatePointer ...` instead.
2021-11-01 13:22:17 +0100 <FOSSHuman[m]> fizzie: Nice!, this seemed to work.. Thanks!
2021-11-01 13:22:42 +0100 <FOSSHuman[m]> Is it because `$` is interpreting the `>> updatePointer` part as an argument to the function?
2021-11-01 13:22:59 +0100 <FOSSHuman[m]> s/function/itself/
2021-11-01 13:23:05 +0100 <FOSSHuman[m]> Haskell noob btw
2021-11-01 13:23:13 +0100 <FOSSHuman[m]> s/the function/itself/
2021-11-01 13:23:14 +0100 <fizzie> Yes. The error message hints at that: it says the second argument of $ is `Go L >> updatePointer ...`.
2021-11-01 13:24:19 +0100 <FOSSHuman[m]> fizzie: Thank you... I should read the compiler errors more closely lol
2021-11-01 13:40:26 +0100cfricke(~cfricke@user/cfricke) (Ping timeout: 268 seconds)
2021-11-01 14:03:30 +0100 <L29Ah> https://tinystash.undef.im/il/5DdZspM6ZPrCkaPJq48tMnpLVbHHoYPjSf9fFC1USk1nEgV9t9xHCfVvv5AKnPDHcyxn… r8 my status workspace and show yours!
2021-11-01 14:04:32 +0100 <liskin> ♥ X201
2021-11-01 14:04:37 +0100alternateved(~user@staticline-31-183-149-3.toya.net.pl)
2021-11-01 14:04:46 +0100 <L29Ah> in fact that's x210
2021-11-01 14:05:47 +0100 <liskin> in that case, replicate 5 '♥'
2021-11-01 14:06:14 +0100 <liskin> although the core temperature is a bit on the highed side then
2021-11-01 14:06:29 +0100 <liskin> I'd expect a modern cpu to stay below 40
2021-11-01 14:07:58 +0100 <L29Ah> it's limited at 95C
2021-11-01 14:08:16 +0100 <L29Ah> a modern cpu will reach as much as you let it to on a laptop cooling system
2021-11-01 14:08:26 +0100 <Solid> I think my x220 also hits 55 or so with a second monitor connected
2021-11-01 14:08:40 +0100 <L29Ah> i5 can easily produce 40+W worth of heat while the cooling system can take 20W max
2021-11-01 14:08:53 +0100 <Solid> (but that things old and some screws are glued in place so I can't even change the thermal paste on the cpu :/)
2021-11-01 14:08:55 +0100 <liskin> well mine is now at 41, docked, just paused a youtube video
2021-11-01 14:09:05 +0100 <liskin> i7-7500U
2021-11-01 14:09:06 +0100 <Solid> s/things/thing's/
2021-11-01 14:10:16 +0100 <L29Ah> and on the lower side it's as cold as noisy your fan is
2021-11-01 14:10:17 +0100 <liskin> it's normally limited to 80, because I haven't bothered with any of the throttled hacks, I like my laptop cool
2021-11-01 14:10:36 +0100 <liskin> L29Ah: 41 without a fan
2021-11-01 14:10:47 +0100L29Ahsometimes wishes to have dock plugs for liquid cooling
2021-11-01 14:10:49 +0100 <Solid> mine almost melts through my desk when compiling :)
2021-11-01 14:10:51 +0100 <liskin> it does kick in around 43 or something
2021-11-01 14:11:18 +0100 <L29Ah> liskin: nice, what's the device?
2021-11-01 14:11:33 +0100 <L29Ah> and ambient temperature
2021-11-01 14:11:33 +0100 <liskin> but for some strange reason the CPU started switching to a 65C limit lately
2021-11-01 14:11:51 +0100 <liskin> L29Ah: T25
2021-11-01 14:11:57 +0100 <liskin> vanilla, no mods
2021-11-01 14:12:08 +0100 <liskin> ambient temp around 21 I think
2021-11-01 14:12:59 +0100 <liskin> it's already out of warranty so I may eventually need to replace it with a 51nb something
2021-11-01 14:13:09 +0100 <liskin> or just get used to the "modern" keyboard :-/
2021-11-01 14:13:49 +0100 <L29Ah> i'm pissed with the firmware quality of 51nb, but still it seems to be the only decent option on the market these days
2021-11-01 14:14:12 +0100 <liskin> yeah, that's what I'm worried about
2021-11-01 14:14:33 +0100 <liskin> as I understand it, even the T480/25 frankenpad has issues with not all keys working as they should
2021-11-01 14:14:49 +0100 <L29Ah> 16:11:51]<liskin> L29Ah: T25
2021-11-01 14:14:49 +0100 <L29Ah> can you please show the steady output of https://github.com/l29ah/intel-powermon/ at max load?
2021-11-01 14:15:07 +0100 <liskin> so I'm kind of hoping they release something for the 30th anniversary, but at this point nobody cares any more :-/
2021-11-01 14:15:30 +0100 <liskin> L29Ah: I have a meeting now but remind me later today
2021-11-01 14:15:35 +0100 <L29Ah> alright
2021-11-01 14:27:35 +0100gruntsplatter(~sogens@gateway/vpn/pia/sogens) (Quit: WeeChat 3.3)
2021-11-01 14:31:37 +0100cfricke(~cfricke@user/cfricke)
2021-11-01 14:50:28 +0100 <liskin> L29Ah: https://gist.github.com/1f8e901a82bd89b48c5beafa2c64c06d - building xmonad-contrib with -j, temp slowly raised up to the 80 ceiling during the first minute or so
2021-11-01 14:51:00 +0100 <liskin> I can try to raise the limit to 95 and see what happens
2021-11-01 14:51:32 +0100 <L29Ah> this sounds like your CPU is throttled into oblivion
2021-11-01 14:52:09 +0100 <liskin> well it's a U, of course it's throttled into oblivion :-)
2021-11-01 14:52:10 +0100 <L29Ah> but still the cooling system is somewhat better than X201's
2021-11-01 14:52:35 +0100 <liskin> but I'm not getting messages about it being throttled, which is a bit weird
2021-11-01 14:52:50 +0100 <liskin> I used to get those in dmesg before, but they stopped once I undervolted
2021-11-01 14:53:08 +0100 <liskin> so there are probably two different throttling mechanisms
2021-11-01 14:53:29 +0100 <L29Ah> 8% better
2021-11-01 14:53:48 +0100 <L29Ah> liskin: yeah by trottling i mean absolute frequency cap
2021-11-01 14:54:03 +0100 <L29Ah> not the situational cap due to overheating
2021-11-01 14:54:12 +0100 <liskin> L29Ah: oh, right
2021-11-01 14:55:16 +0100 <L29Ah> can be illustrated by `sysbench cpu run --threads=9 --time=5`
2021-11-01 14:55:22 +0100 <L29Ah> 42233 here
2021-11-01 14:55:25 +0100 <liskin> hm, those numbers look almost the same with the limit raised to 95
2021-11-01 14:55:48 +0100 <L29Ah> but does actual temperature rise to 95?
2021-11-01 14:55:58 +0100 <liskin> not really, barely gets to 80
2021-11-01 14:56:03 +0100 <liskin> I'll need to run stack in a loop
2021-11-01 14:56:25 +0100 <liskin> or power the nvidia up to stress the cooling system a bit
2021-11-01 14:58:55 +0100 <liskin> https://gist.github.com/0e84c03f0dea1fa066395ed54b7b7769 - ghc -j + primusrun glxgears
2021-11-01 14:59:09 +0100 <liskin> 3.5k fan rpm, 83C tops
2021-11-01 14:59:57 +0100 <liskin> I think I might need to write to another MSR to override the wattage cap, not just the thermal cap
2021-11-01 15:03:14 +0100kr1x(~kriket@170.249.0.122) (Ping timeout: 260 seconds)
2021-11-01 15:05:16 +0100kr1x(kriket@gateway/vpn/protonvpn/kr1x)
2021-11-01 15:07:53 +0100 <liskin> hm, it's weird, I raised the wattage caps, but it still draws under 20 watts, and when I check with turbostat, all 4 cores are at their turbo frequencies all the time
2021-11-01 15:08:18 +0100 <liskin> maybe ghc is too lazy :-)
2021-11-01 15:10:29 +0100kr1x(kriket@gateway/vpn/protonvpn/kr1x) (Ping timeout: 268 seconds)
2021-11-01 15:11:34 +0100kr1x(~kriket@170.249.0.122)
2021-11-01 15:16:22 +0100 <FOSSHuman[m]> https://github.com/AdnanHodzic/auto-cpufreq
2021-11-01 15:17:20 +0100 <FOSSHuman[m]> This can greatly extend the battery life of a laptop, it automatically adjusts the CPU frequency
2021-11-01 15:30:12 +0100kr1x(~kriket@170.249.0.122) (Ping timeout: 268 seconds)
2021-11-01 15:31:40 +0100 <L29Ah> FOSSHuman[m]: i'm skeptical of the utility of this program
2021-11-01 15:31:53 +0100kr1x(kriket@gateway/vpn/protonvpn/kr1x)
2021-11-01 15:32:19 +0100 <L29Ah> as it assumes that CPU is the sole power consumer, and you don't need the results of CPU work
2021-11-01 15:33:03 +0100 <L29Ah> and/or additional waiting for the result is acceptable
2021-11-01 15:35:00 +0100 <L29Ah> sure you can increase computations per joule if you lower the frequency somewhat, but it becomes interestingly nonlinear when the power consumption of other system components, notably LCD backlight, is brought into the equation
2021-11-01 15:36:57 +0100 <L29Ah> and advanced techniques like race-to-idle bring even more confusion
2021-11-01 15:37:27 +0100L29Ahis disappointed by the lack of benchmarks in README
2021-11-01 15:43:21 +0100kr1x(kriket@gateway/vpn/protonvpn/kr1x) (Remote host closed the connection)
2021-11-01 15:47:50 +0100 <liskin> L29Ah: I just checked the picom slowness, and I had to revert both the commits you mentioned to get to a reasonable performance
2021-11-01 15:49:11 +0100kr1x(~kriket@170.249.0.122)
2021-11-01 15:50:45 +0100 <L29Ah> liskin: try noting that in the issue, as it seems like the maintainer have dismissed my concerns
2021-11-01 15:50:57 +0100 <L29Ah> fwiw i have no clue how it works, if it's picom or xmonad or other apps' windows to blame, i just bisected it
2021-11-01 15:52:29 +0100 <liskin> I think I have an idea what's going on
2021-11-01 15:52:53 +0100 <liskin> in https://github.com/yshui/picom/issues/381 I see no answer from the maintainer
2021-11-01 15:56:02 +0100 <liskin> L29Ah: without the free_paint_glx change reverted, glx_find_fbconfig is called more than 10 times on every xmonad layout resize
2021-11-01 15:56:58 +0100 <liskin> dunno what that function does exactly, but it feels like it should be called once, not a hundred times every time something changes
2021-11-01 15:59:06 +0100 <liskin> the other commit just makes glx_find_fbconfig slower
2021-11-01 16:04:52 +0100 <liskin> I think glx_find_fbconfig just needs some memoization/caching and it will be good
2021-11-01 16:05:10 +0100 <liskin> the range of its inputs is quite small
2021-11-01 16:18:12 +0100kr1x(~kriket@170.249.0.122) (Quit: .)
2021-11-01 16:44:42 +0100cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.3)
2021-11-01 17:25:30 +0100qbt(~qbt@user/edun) (Quit: Leaving.)
2021-11-01 17:42:10 +0100alternateved(~user@staticline-31-183-149-3.toya.net.pl) (Ping timeout: 268 seconds)
2021-11-01 18:03:14 +0100seschwar(~seschwar@user/seschwar)
2021-11-01 20:05:01 +0100qbt(~qbt@user/edun)
2021-11-01 20:05:25 +0100qbt(~qbt@user/edun) (Client Quit)
2021-11-01 20:28:45 +0100gruntsplatter(~sogens@gateway/vpn/pia/sogens)
2021-11-01 20:53:20 +0100steve__(~steve@ool-182c2aa4.dyn.optonline.net) (Read error: Connection reset by peer)
2021-11-01 20:53:37 +0100steve__(~steve@ool-182c2aa4.dyn.optonline.net)
2021-11-01 20:55:27 +0100qbt(~qbt@user/edun)
2021-11-01 20:55:32 +0100qbt(~qbt@user/edun) (Client Quit)
2021-11-01 22:00:19 +0100Extropy(~extropy@user/extropy)
2021-11-01 22:00:32 +0100alternateved(~user@staticline-31-183-149-3.toya.net.pl)
2021-11-01 22:03:37 +0100charlie39(~charlie39@223.238.124.49)
2021-11-01 22:11:09 +0100charlie39(~charlie39@223.238.124.49) ()
2021-11-01 22:32:15 +0100mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2021-11-01 23:43:10 +0100alternateved(~user@staticline-31-183-149-3.toya.net.pl) (Ping timeout: 260 seconds)