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

User modes aren't propagated via IRC relay protocol #1984

Closed
TehPeGaSuS opened this issue Jul 21, 2023 · 0 comments
Closed

User modes aren't propagated via IRC relay protocol #1984

TehPeGaSuS opened this issue Jul 21, 2023 · 0 comments
Assignees
Labels
bug Unexpected problem or unintended behavior
Milestone

Comments

@TehPeGaSuS
Copy link

Bug summary

When connecting to weechat via IRC relay protocol with another weechat instance, the user modes aren't propagated and we end up not having any user/server modes on the instance connected via the IRC relay protocol.

Steps to reproduce

1. Connect one weechat instance directly to an IRC server
2. Connect another weechat instance via IRC relay protocol to the instance directly connected to the IRC server
3.  Compare the user modes on both instances. While the instance directly connected to the IRC server has the user and server modes displayed correctly, the instance connected via the IRC relay protocol has no user/server modes set

Current behavior

weechat<->IRC shows the current user and server modes but weechat<->weechat (via IRC relay) doesn't

Expected behavior

User modes should be the same on the weechat<->IRC and weechat<->weechat connection

Suggested solutions

Additional information

Weechat via IRC relay protocol:
weechat_irc_relay

Weechat via direct connection:
weechat_direct_connection


  • WeeChat version: WeeChat 4.1.0-dev (git: v4.0.0-66-g13241cdca) [compiled on Jul 21 2023 11:47:37]
  • OS, distribution and version: Ubuntu 22.04.2 LTS
  • Terminal: xfce4-terminal
  • Terminal multiplexer (screen/tmux/…/none): tmux
@TehPeGaSuS TehPeGaSuS added the bug Unexpected problem or unintended behavior label Jul 21, 2023
@flashcode flashcode self-assigned this Aug 13, 2023
@flashcode flashcode added this to the 4.1.0 milestone Aug 13, 2023
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

2 participants