2024/09/28

Newest at the top

2024-09-28 16:51:33 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) wz1000
2024-09-28 16:41:21 +0200\f_\f
2024-09-28 16:41:19 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Ping timeout: 265 seconds)
2024-09-28 16:41:18 +0200red-snail(~snail@static.151.210.203.116.clients.your-server.de) (Ping timeout: 265 seconds)
2024-09-28 16:41:17 +0200\f(4c1975b719@user/f/x-7101985) (Ping timeout: 265 seconds)
2024-09-28 16:36:50 +0200red-snail1(~snail@static.151.210.203.116.clients.your-server.de)
2024-09-28 16:35:43 +0200\f_(4c1975b719@user/f/x-7101985) \f
2024-09-27 22:24:27 +0200yaslam(~yaslam@user/yaslam) yaslam
2024-09-27 21:31:42 +0200yaslam(~yaslam@user/yaslam) (Read error: Connection reset by peer)
2024-09-27 20:10:36 +0200whereiseveryone_whereiseveryone
2024-09-27 20:10:35 +0200\f_\f
2024-09-27 20:10:31 +0200whereiseveryone(206ba86c98@2a03:6000:1812:100::2e4) (*.net *.split)
2024-09-27 20:10:30 +0200\f(4c1975b719@user/f/x-7101985) (*.net *.split)
2024-09-27 20:04:29 +0200whereiseveryone_(206ba86c98@2a03:6000:1812:100::2e4) whereiseveryone
2024-09-27 20:04:21 +0200\f_(4c1975b719@user/f/x-7101985) \f
2024-09-27 15:48:35 +0200b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2024-09-27 09:55:36 +0200b50d(~b50d@62.96.54.30)
2024-09-26 21:20:13 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) wz1000
2024-09-26 21:20:13 +0200red-snail(~snail@static.151.210.203.116.clients.your-server.de) red-snail
2024-09-26 21:19:33 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (*.net *.split)
2024-09-26 21:19:32 +0200red-snail(~snail@static.151.210.203.116.clients.your-server.de) (*.net *.split)
2024-09-26 17:54:21 +0200red-snail(~snail@static.151.210.203.116.clients.your-server.de) red-snail
2024-09-26 16:52:52 +0200b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2024-09-26 10:01:28 +0200b50d(~b50d@62.96.54.30)
2024-09-25 23:16:08 +0200yaslam(~yaslam@user/yaslam) yaslam
2024-09-25 23:13:57 +0200yaslam(~yaslam@user/yaslam) (Ping timeout: 248 seconds)
2024-09-25 16:09:15 +0200b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2024-09-25 15:50:07 +0200 <bitozoid> I can figure out how it could be the other way. Any hint?
2024-09-25 15:48:48 +0200 <bitozoid> "This can be used to create [...] a key that can still function as a normal key, but also as a leader key when used slowly."
2024-09-25 15:48:09 +0200 <bitozoid> When talking about 'around-next-timeout':
2024-09-25 15:47:17 +0200 <bitozoid> Hi! I've got a question about the tutorial.
2024-09-25 15:46:37 +0200bitozoid(~bitozoid@user/bitozoid) bitozoid
2024-09-25 12:57:50 +0200Piraty_Piraty
2024-09-25 08:18:11 +0200b50d(~b50d@62.96.54.30)
2024-09-25 07:19:01 +0200aswjrisp(~aswjrisp@user/aswjrisp) aswjrisp
2024-09-25 07:14:06 +0200aswjrisp(~aswjrisp@user/aswjrisp) (Remote host closed the connection)
2024-09-24 18:14:04 +0200Solid(~slot@xmonad/slotThe) slot
2024-09-24 18:12:04 +0200Solid(~slot@xmonad/slotThe) (Quit: Connection reset by pear)
2024-09-24 16:33:30 +0200b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2024-09-24 13:26:23 +0200aswjrisp(~aswjrisp@user/aswjrisp) aswjrisp
2024-09-24 13:21:03 +0200aswjrisp(~aswjrisp@user/aswjrisp) (Remote host closed the connection)
2024-09-24 09:42:41 +0200b50d(~b50d@62.96.54.30)
2024-09-23 19:06:54 +0200Server+nt
2024-09-23 19:06:54 +0200ircbrowse_tom(~ircbrowse@user/tomsmeding/bot/ircbrowse-tom) ircbrowse_tom
2024-09-23 18:58:35 +0200Server+nt
2024-09-23 18:58:32 +0200ircbrowse_tom(~ircbrowse@user/tomsmeding/bot/ircbrowse-tom) ircbrowse_tom
2024-09-23 18:36:13 +0200Server+nt
2024-09-23 18:36:13 +0200ircbrowse_tom(~ircbrowse@user/tomsmeding/bot/ircbrowse-tom)
2024-09-23 15:52:28 +0200b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2024-09-23 09:40:20 +0200b50d(~b50d@62.96.54.30)