ZNC LISTCHANS is floody when it doesn't have to be. #538

New Issue

2026-10-05T04:28:32+02:00

adam commented

2026-10-05 04:28:32 +02:00

Due to the new CTable implementation ZNC LISTCHANS gets extremely floody when it doesn't have to be.

Currently, it produces this type of output:

(00:19:37) <*status> Name: @#channel1
(00:19:37) <*status> Status: Joined
(00:19:37) <*status> ------
(00:19:37) <*status> Name: #channel2
(00:19:37) <*status> Status: Disabled
(00:19:37) <*status> ------
(00:19:37) <*status> Name: @#channel3
(00:19:37) <*status> Status: Joined
(00:19:37) <*status> ------
(00:19:37) <*status> Name: @+#channel4
(00:19:37) <*status> Status: Joined
(00:19:37) <*status> ------
(00:19:37) <*status> Name: #channel5
(00:19:37) <*status> Status: Joined
(00:19:37) <*status> ------
(00:19:37) <*status> Total: 11 - Joined: 10 - Detached: 0 - Disabled: 1

In previous ZNC versions, I recall it looking more like this:

(00:19:37) <*status> ------------+-----------+
(00:19:37) <*status> Name        | Status    |
(00:19:37) <*status> ------------+-----------+
(00:19:37) <*status> @#channel1  | Joined    |
(00:19:37) <*status> #channel2   | Disabled  |
(00:19:37) <*status> @#channel3  | Joined    |
(00:19:37) <*status> @+#channel4 | Joined    |
(00:19:37) <*status> #channel5   | Joined    |
(00:19:37) <*status> ------------+-----------+

Which I think is a lot less spammy, and a lot more appealing. Although I can imagine due to how CTable was changed an approach where name and status are on the same line would be easier to achieve and still achieve a similar result. (Although I suppose tables aren't really needed in that case, and you can just print it normally as a string.)

The code can be found here:
https://github.com/znc/znc/blob/a3ed8147d0c575e7f3d69e5ee3bbe084f1b4d780/src/ClientCommand.cpp#L525-L544

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Due to the new CTable implementation ZNC LISTCHANS gets extremely floody when it doesn't have to be. Currently, it produces this type of output: ``` (00:19:37) <*status> Name: @#channel1 (00:19:37) <*status> Status: Joined (00:19:37) <*status> ------ (00:19:37) <*status> Name: #channel2 (00:19:37) <*status> Status: Disabled (00:19:37) <*status> ------ (00:19:37) <*status> Name: @#channel3 (00:19:37) <*status> Status: Joined (00:19:37) <*status> ------ (00:19:37) <*status> Name: @+#channel4 (00:19:37) <*status> Status: Joined (00:19:37) <*status> ------ (00:19:37) <*status> Name: #channel5 (00:19:37) <*status> Status: Joined (00:19:37) <*status> ------ (00:19:37) <*status> Total: 11 - Joined: 10 - Detached: 0 - Disabled: 1 ``` In previous ZNC versions, I recall it looking more like this: ``` (00:19:37) <*status> ------------+-----------+ (00:19:37) <*status> Name | Status | (00:19:37) <*status> ------------+-----------+ (00:19:37) <*status> @#channel1 | Joined | (00:19:37) <*status> #channel2 | Disabled | (00:19:37) <*status> @#channel3 | Joined | (00:19:37) <*status> @+#channel4 | Joined | (00:19:37) <*status> #channel5 | Joined | (00:19:37) <*status> ------------+-----------+ ``` Which I think is a lot less spammy, and a lot more appealing. Although I can imagine due to how CTable was changed an approach where name and status are on the same line would be easier to achieve and still achieve a similar result. (Although I suppose tables aren't really needed in that case, and you can just print it normally as a string.) The code can be found here: https://github.com/znc/znc/blob/a3ed8147d0c575e7f3d69e5ee3bbe084f1b4d780/src/ClientCommand.cpp#L525-L544 ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/24283578-znc-listchans-is-floody-when-it-doesn-t-have-to-be?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam closed this issue

2026-10-05 04:28:33 +02:00

adam commented

2026-10-05 04:28:33 +02:00