Newest at the top
| 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 :) |
| 2025-05-16 01:28:56 +0200 | <haskellbridge> | <sm> I mean, intermittent 5m slices of channel history isn't very useful to him either |
| 2025-05-16 01:28:55 +0200 | <monochrom> | But you can count me biased because I am not affected by other people frequently cycling. |
| 2025-05-16 01:27:50 +0200 | <haskellbridge> | <sm> or configure his mac differently ? or his irc client ? out of kind regard for the room ? |
| 2025-05-16 01:27:41 +0200 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-05-16 01:27:27 +0200 | <monochrom> | I use a bouncer, but I don't want to be imposing and say "everyone must shell out extra money for an extra PC or shell account to run a bouncer". |
| 2025-05-16 01:26:41 +0200 | <haskellbridge> | <sm> perhaps he should use a bouncer like me ? |
| 2025-05-16 01:26:34 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-05-16 01:26:11 +0200 | <haskellbridge> | <sm> 👀 |
| 2025-05-16 01:25:55 +0200 | <monochrom> | A long time ago merijn explained it. Something about macOS going to sleep then waking up on LAN. |
| 2025-05-16 01:22:40 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-05-16 01:21:54 +0200 | Lord_of_Life_ | Lord_of_Life |
| 2025-05-16 01:21:41 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-16 01:20:31 +0200 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2025-05-16 01:20:25 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 244 seconds) |
| 2025-05-16 01:20:01 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2025-05-16 01:16:50 +0200 | <EvanR> | sm: the C channel soft kickbans you if you leave and join twice too quickly |
| 2025-05-16 01:15:46 +0200 | <TMA> | my theory is invalidated |
| 2025-05-16 01:13:21 +0200 | <haskellbridge> | <sm> merijn didn't respond last time I pinged, maybe an IRC op could reach them ? |
| 2025-05-16 01:11:18 +0200 | <Clint> | close enough |
| 2025-05-16 01:11:13 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds) |
| 2025-05-16 01:11:06 +0200 | Clint | squints. |
| 2025-05-16 01:10:52 +0200 | <haskellbridge> | <sm> disconnecting in 5.. 4.. |
| 2025-05-16 01:08:38 +0200 | manwithluck | (~manwithlu@2a09:bac5:5082:2387::38a:10) manwithluck |
| 2025-05-16 01:08:05 +0200 | manwithluck | (~manwithlu@2a09:bac5:5084:2387::38a:3b) (Ping timeout: 248 seconds) |
| 2025-05-16 01:07:45 +0200 | <sm> | merijn, pinging you again about your IRC connection, please respond if you can see this |
| 2025-05-16 01:07:44 +0200 | xff0x | (~xff0x@2405:6580:b080:900:7ed8:b8a6:621a:b979) (Ping timeout: 260 seconds) |
| 2025-05-16 01:07:28 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-05-16 01:07:00 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |