From 4544c4b56eae07e9da7ed0b4b0329b2989494f0b Mon Sep 17 00:00:00 2001 From: Luke Bratch Date: Sun, 9 Apr 2023 03:17:18 +0200 Subject: Fix ban list request handling - support both "MODE #channel b" and "MODE #channel +b". --- TODO | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) (limited to 'TODO') diff --git a/TODO b/TODO index c29c3ba..c65634f 100644 --- a/TODO +++ b/TODO @@ -24,13 +24,6 @@ Do connectcommands happen on reconnect? Are "no such nick/channel" messages as shown in clients correct compared to non-(bla)bouncer clients? -Support ban list when requesting /mode #channel +b (commands 367 and 368 at least) - ensure max ban list length is supported. example: -:irc.tghost.co.uk 367 l_bratch #foo *!foo@bar.bz l_bratch 1642588731 -:irc.tghost.co.uk 367 l_bratch #foo *!*bbuser@*.bratch.co.uk l_bratch 1642588681 -:irc.tghost.co.uk 368 l_bratch #foo :End of Channel Ban List -Or if there are no bans then just 368: -:irc.tghost.co.uk 368 l_bratch #foo :End of Channel Ban List - Other IRC clients log stuff like "Mar 31 16:58:15 * #foobar :No topic is set." - can/should we? Git version in code. @@ -47,4 +40,6 @@ Debug log ("checking client socket out of ") gets busy after fdmax ge BLABOUNCER/stdin functions to add: - List connected/authenticated clients +KICK not handled. + Crash when requesting 30 hour replay. -- cgit v1.2.3