Newest at the top
| 2025-05-16 03:04:21 +0200 | Square | (~Square4@user/square) (Ping timeout: 248 seconds) |
| 2025-05-16 03:03:28 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2025-05-16 03:01:19 +0200 | Square2 | (~Square@user/square) Square |
| 2025-05-16 02:58:13 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 02:51:26 +0200 | tolgo | (~Thunderbi@199.115.144.130) (Quit: tolgo) |
| 2025-05-16 02:47:04 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2025-05-16 02:42:50 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 02:40:53 +0200 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 248 seconds) |
| 2025-05-16 02:40:38 +0200 | tolgo | (~Thunderbi@199.115.144.130) |
| 2025-05-16 02:34:47 +0200 | califax | (~califax@user/califx) califx |
| 2025-05-16 02:32:15 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2025-05-16 02:32:14 +0200 | pavonia | (~user@user/siracusa) siracusa |
| 2025-05-16 02:31:48 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2025-05-16 02:24:49 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 02:17:54 +0200 | ljdarj1 | ljdarj |
| 2025-05-16 02:17:54 +0200 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 245 seconds) |
| 2025-05-16 02:16:03 +0200 | ljdarj1 | (~Thunderbi@user/ljdarj) ljdarj |
| 2025-05-16 02:13:51 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-05-16 02:11:09 +0200 | visilii | (~visilii@85.94.27.197) |
| 2025-05-16 02:10:32 +0200 | ttybitnik | (~ttybitnik@user/wolper) (Quit: Fading out...) |
| 2025-05-16 02:09:02 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 02:06:45 +0200 | visilii | (~visilii@81.177.126.61) (Ping timeout: 248 seconds) |
| 2025-05-16 02:03:18 +0200 | jespada | (~jespada@r179-25-150-22.dialup.adsl.anteldata.net.uy) (Ping timeout: 276 seconds) |
| 2025-05-16 01:58:24 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-05-16 01:53:16 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 01:50:45 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-05-16 01:50:14 +0200 | jespada | (~jespada@r179-25-150-22.dialup.adsl.anteldata.net.uy) jespada |
| 2025-05-16 01:50:12 +0200 | sp1ff | (~user@c-67-160-173-55.hsd1.wa.comcast.net) (Read error: Connection reset by peer) |
| 2025-05-16 01:49:13 +0200 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 265 seconds) |
| 2025-05-16 01:48:18 +0200 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 252 seconds) |
| 2025-05-16 01:43:55 +0200 | jespada | (~jespada@r179-25-20-56.dialup.adsl.anteldata.net.uy) (Ping timeout: 252 seconds) |
| 2025-05-16 01:42:16 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-05-16 01:38:12 +0200 | sajenim | (~sajenim@user/sajenim) sajenim |
| 2025-05-16 01:37:28 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 01:35:23 +0200 | <EvanR> | another improvement discord made on IRC, no one knows who joined or quit xD |
| 2025-05-16 01:34:48 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 272 seconds) |
| 2025-05-16 01:34:45 +0200 | <EvanR> | and fixing merijn's connection will not save you from it happening to some random other person, but a specific client would |
| 2025-05-16 01:34:15 +0200 | <EvanR> | yeah a specific client could discard specifically merijn's join quits |
| 2025-05-16 01:33:53 +0200 | flounders | (~flounders@2607:fb90:ee09:4f99:c6b8:4dd2:346a:a4b4) flounders |
| 2025-05-16 01:33:19 +0200 | acidjnk | (~acidjnk@p200300d6e71c4f453148b790f5eba778.dip0.t-ipconnect.de) (Ping timeout: 245 seconds) |
| 2025-05-16 01:33:01 +0200 | <haskellbridge> | <sm> sure, but the root cause is merijn |
| 2025-05-16 01:32:49 +0200 | int-e | shrugs |
| 2025-05-16 01:32:43 +0200 | <int-e> | this entire "problem" is client specific |
| 2025-05-16 01:32:22 +0200 | <haskellbridge> | <sm> I don't know what that means, it sounds client specific |
| 2025-05-16 01:31:59 +0200 | <int-e> | they're in the (back-)log, but the channel doesn't show as active when somebody parts or joins |
| 2025-05-16 01:31:24 +0200 | <haskellbridge> | <sm> They do for some of us int-e, as in my screenshot. Having to turn those off entirely and sacrifice all join/leave awareness because of one person's config is silly, don't you think ? |
| 2025-05-16 01:30:46 +0200 | <int-e> | And it's pretty far off topic. |
| 2025-05-16 01:30:19 +0200 | <int-e> | I for one am more bothered by this discussion than by merijns rejoins and no, I'm not ignoring those. Why? Because they don't show up as channel activity. |
| 2025-05-16 01:30:08 +0200 | <monochrom> | Oh, I have long accepted that people who learn from history are bound to helplessly watch other people repeat it! |
| 2025-05-16 01:29:45 +0200 | <haskellbridge> | <sm> I will drop this urgent matter for now :) |