2025/11/18

Newest at the top

2025-11-18 16:02:25 +0100rembo10_(~rembo10@main.remulis.com)
2025-11-18 16:02:15 +0100Xe_(~Xe@perl/impostor/xe) Xe
2025-11-18 15:59:11 +0100statusbot(~statusbot@ec2-34-198-122-184.compute-1.amazonaws.com) statusbot
2025-11-18 15:59:04 +0100ss4(~wootehfoo@user/wootehfoot) wootehfoot
2025-11-18 15:57:59 +0100 <haskellbridge> <Morj> Nope
2025-11-18 15:57:53 +0100 <lucabtz> Morj: test
2025-11-18 15:57:48 +0100 <lucabtz> how about the colon?
2025-11-18 15:57:02 +0100fp(~Thunderbi@2001:708:150:10::7e06) (Ping timeout: 265 seconds)
2025-11-18 15:52:59 +0100 <haskellbridge> <Morj> Yep, no notif
2025-11-18 15:52:54 +0100 <tomsmeding> Morj test
2025-11-18 15:52:48 +0100 <haskellbridge> <Morj> Try now plz
2025-11-18 15:52:43 +0100morj(~morj@user/morj) (Konversation terminated!)
2025-11-18 15:52:37 +0100 <haskellbridge> <Morj> Huh
2025-11-18 15:52:26 +0100 <tomsmeding> Morj: so it's possible that it works _because_ you're now also here with your morj irc user
2025-11-18 15:51:35 +0100SlackCoder(~SlackCode@64-94-63-8.ip.weststar.net.ky) (Ping timeout: 245 seconds)
2025-11-18 15:51:31 +0100 <tomsmeding> https://github.com/hifi/heisenbridge/issues/310
2025-11-18 15:50:20 +0100 <tomsmeding> oh right, I remember
2025-11-18 15:50:10 +0100 <haskellbridge> <Morj> It's not the matrix itself (which also has a million problems), but the bridge misbehaving. But I believe this problem was reported
2025-11-18 15:49:48 +0100 <tomsmeding> that's a relief
2025-11-18 15:49:29 +0100 <haskellbridge> <Morj> Yes, it's uncorrelated
2025-11-18 15:49:08 +0100 <tomsmeding> Morj: have you considered correlating matrix notification behaviour with the phase of the moon
2025-11-18 15:47:37 +0100 <haskellbridge> <Morj> Um, now I see both (I was just afk)
2025-11-18 15:43:04 +0100Zemy(~Zemy@2600:100c:b0ae:c0b:84d9:a0ff:fe3d:6f11) (Ping timeout: 256 seconds)
2025-11-18 15:40:30 +0100Zemy_(~Zemy@syn-192-154-181-091.biz.spectrum.com)
2025-11-18 15:39:59 +0100 <dutchie> Morj: there was no colon on the second one
2025-11-18 15:39:58 +0100 <tomsmeding> Morj test
2025-11-18 15:39:55 +0100pr1sm(~pr1sm@24.91.163.31)
2025-11-18 15:32:07 +0100 <haskellbridge> <Morj> What are you all doing wrong?
2025-11-18 15:31:50 +0100 <haskellbridge> <Morj> Wait what, this one tagged me
2025-11-18 15:31:40 +0100 <morj> Morj hm
2025-11-18 15:31:35 +0100 <haskellbridge> <Morj> morj: Hm
2025-11-18 15:31:24 +0100 <morj> The tagging of my bridged account still doesn't work, but what if I write out @morj:morj.men ?
2025-11-18 15:30:58 +0100morj(~morj@user/morj) morj
2025-11-18 15:29:05 +0100 <haskellbridge> <Morj> Thanks, that's exactly what I wanted
2025-11-18 15:27:17 +0100 <Leary> Morj: `GHC.Num.integerLog2`
2025-11-18 15:24:46 +0100rekahsoft(~rekahsoft@70.51.99.245) rekahsoft
2025-11-18 15:20:25 +0100srazkvt(~sarah@user/srazkvt) srazkvt
2025-11-18 15:18:26 +0100 <lucabtz> sure sure, i just meant its related to log2, didnt know about the specific haskell functions
2025-11-18 15:16:39 +0100Zemy_(~Zemy@72.178.108.235) (Ping timeout: 244 seconds)
2025-11-18 15:14:19 +0100CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 260 seconds)
2025-11-18 15:13:55 +0100 <haskellbridge> <Morj> I don't care about efficiency in ghci, more about usefulness
2025-11-18 15:13:52 +0100Zemy(~Zemy@2600:100c:b0ae:c0b:84d9:a0ff:fe3d:6f11)
2025-11-18 15:13:41 +0100 <haskellbridge> <Morj> It's not only not good for efficiency, but logBase 2 (2^1024) == NaN
2025-11-18 15:12:00 +0100vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 245 seconds)
2025-11-18 15:11:56 +0100weary-traveler(~user@user/user363627) (Remote host closed the connection)
2025-11-18 15:10:09 +0100trickard_trickard
2025-11-18 15:08:46 +0100Lycurgus(~juan@user/Lycurgus) (bye room!)
2025-11-18 15:08:28 +0100 <lucabtz> that's why i said maybe not good for efficiency
2025-11-18 15:07:37 +0100 <lucabtz> Morj by log2 i didnt mean anything specific about haskell, just the natural logarithm in base 2, but you are right it is for floating
2025-11-18 15:02:25 +0100srazkvt(~sarah@user/srazkvt) (Ping timeout: 264 seconds)