Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

account-notify causes /who spam in server buffer #2108

Open
NetSysFire opened this issue Apr 19, 2024 · 0 comments
Open

account-notify causes /who spam in server buffer #2108

NetSysFire opened this issue Apr 19, 2024 · 0 comments
Labels
bug Unexpected problem or unintended behavior

Comments

@NetSysFire
Copy link
Contributor

Describe the bug

When I join channels, I get an unfunny amount of /who spam in my server buffer (set to independent for reference).
This is new and happened ever since I enabled account-notify and extended-join. People in #weechat tell me its probably account-notify and not extended-join. Whatever it does, it is also the thing that colors nicks that are away green (by default) in the nicklist I think.

Steps to reproduce

First of all: This is a relay setup. My local weechat connects to my bouncer, which is another weechat of the same version that is configured as a relay in IRC mode. Both have the same capabilities enabled (except the client, which additionally has server-time). I do not get the spam on the relay (very minimal setup there, does not have nicklist), only on this local client. /cycleing on the local client does cause a /who to be issued.

  1. Make your relay reconnect to the network or join a channel you have not joined before. Or /cycle a channel.
  2. The server buffer will be filled with the /who output, including End of /WHO list., indicating it must be issued by the local client.

Current behavior

Spam.

Expected behavior

The output goes to /dev/null.

Suggested solutions

No response

Additional information

No response

WeeChat version

4.2.2-2

What OS are you using?

Relay: Ubuntu 20.04, local client: Arch Linux

On which terminal are you running WeeChat?

kitty

Which terminal multiplexer are you using?

none

@NetSysFire NetSysFire added the bug Unexpected problem or unintended behavior label Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant