2026/04/01

Newest at the top

2026-04-01 14:01:58 +0200divlamir(~divlamir@user/divlamir) (Read error: Connection reset by peer)
2026-04-01 13:43:48 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 255 seconds)
2026-04-01 13:39:02 +0200czan(~czan@user/mange) czan
2026-04-01 12:53:23 +0200fp1(~Thunderbi@2001:708:20:1406::1370) fp
2026-04-01 12:45:58 +0200CiaoSen(~Jura@p549cb690.dip0.t-ipconnect.de) CiaoSen
2026-04-01 12:43:17 +0200xff0x(~xff0x@2405:6580:b080:900:4a9b:f7a0:11a1:60ca)
2026-04-01 12:41:09 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 245 seconds)
2026-04-01 12:36:35 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-01 12:30:38 +0200Square2(~Square4@user/square) Square
2026-04-01 12:29:00 +0200divlamir(~divlamir@user/divlamir) divlamir
2026-04-01 12:27:28 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2026-04-01 12:27:13 +0200lisbeths(uid135845@id-135845.lymington.irccloud.com) lisbeths
2026-04-01 12:24:11 +0200divlamir(~divlamir@user/divlamir) (Ping timeout: 268 seconds)
2026-04-01 12:23:22 +0200gmg(~user@user/gehmehgeh) gehmehgeh
2026-04-01 12:21:12 +0200gmg(~user@user/gehmehgeh) (Ping timeout: 265 seconds)
2026-04-01 12:18:20 +0200divlamir(~divlamir@user/divlamir) divlamir
2026-04-01 12:13:28 +0200divlamir(~divlamir@user/divlamir) (Read error: Connection reset by peer)
2026-04-01 12:11:49 +0200divlamir_divlamir
2026-04-01 12:11:48 +0200divlamir(~divlamir@user/divlamir) (Ping timeout: 256 seconds)
2026-04-01 12:10:33 +0200ChanServ+v haskellbridge
2026-04-01 12:10:33 +0200haskellbridge(~hackager@96.28.224.214) hackager
2026-04-01 12:10:06 +0200CiaoSen(~Jura@p549cb690.dip0.t-ipconnect.de) (Ping timeout: 244 seconds)
2026-04-01 12:08:24 +0200czan(~czan@user/mange) (Ping timeout: 256 seconds)
2026-04-01 12:07:52 +0200divlamir_(~divlamir@user/divlamir) divlamir
2026-04-01 12:07:14 +0200haskellbridge(~hackager@96.28.224.214) (Read error: Connection reset by peer)
2026-04-01 12:03:56 +0200 <tomsmeding> what can one do with a package candidate on hackage? I know you can look at the hackage page to see if documentation etc. (when self-uploaded) is correct, but is there a way to test _using_ the package?
2026-04-01 11:49:19 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-01 11:42:20 +0200xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 256 seconds)
2026-04-01 11:27:17 +0200qqq(~qqq@185.54.20.216) (Remote host closed the connection)
2026-04-01 11:25:34 +0200dutchie(~dutchie@user/dutchie) dutchie
2026-04-01 11:24:29 +0200dutchie(~dutchie@user/dutchie) (Remote host closed the connection)
2026-04-01 11:19:45 +0200Googulator59Googulator
2026-04-01 11:08:34 +0200poscat(~poscat@user/poscat) (Ping timeout: 248 seconds)
2026-04-01 11:06:52 +0200poscat0x04(~poscat@user/poscat) poscat
2026-04-01 10:58:15 +0200lisbeths(uid135845@id-135845.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2026-04-01 10:46:24 +0200srazkvt(~sarah@user/srazkvt) srazkvt
2026-04-01 10:40:58 +0200dhil(~dhil@5.151.29.140) dhil
2026-04-01 10:26:59 +0200emmanuelux(~em@user/emmanuelux) (Ping timeout: 245 seconds)
2026-04-01 10:22:44 +0200acidjnk_new(~acidjnk@p200300d6e700e5734afa4e6ae2fbd9a2.dip0.t-ipconnect.de) acidjnk
2026-04-01 10:18:47 +0200arandombit(~arandombi@user/arandombit) arandombit
2026-04-01 10:18:47 +0200arandombit(~arandombi@2a02:2455:8656:7100:d0b1:e9e0:7ad6:1750) (Changing host)
2026-04-01 10:18:47 +0200arandombit(~arandombi@2a02:2455:8656:7100:d0b1:e9e0:7ad6:1750)
2026-04-01 10:13:18 +0200qqq(~qqq@185.54.20.216)
2026-04-01 10:07:59 +0200merijn(~merijn@77.242.116.146) merijn
2026-04-01 10:04:49 +0200ft(~ft@p508db341.dip0.t-ipconnect.de) (Quit: leaving)
2026-04-01 10:03:10 +0200 <tomsmeding> dminuoso: https://ircbrowse.tomsmeding.com/day/lchaskell/2021/06/16?id=49907#trid49907
2026-04-01 09:34:17 +0200merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-04-01 09:29:43 +0200merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-01 09:24:34 +0200arandombit(~arandombi@user/arandombit) (Ping timeout: 248 seconds)
2026-04-01 09:21:46 +0200tomboy64(~tomboy64@user/tomboy64) tomboy64