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.

Sign up for GitHub

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

Jump to bottom

Slash in channel name prevents sending PRIVMSG due to RELAYMSG #2114

Closed
Mikaela opened this issue Jan 2, 2024 · 1 comment
Closed

Slash in channel name prevents sending PRIVMSG due to RELAYMSG #2114

Mikaela opened this issue Jan 2, 2024 · 1 comment

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Jan 2, 2024

Reported to me by @ccxcz. A channel such as #/dev/null can be created and registered, but sending messages there fails due to #/dev/null: Relayed users cannot receive private messages

  • ergo-2.12.0 etro.mikaela.info
@Mikaela
Copy link
Contributor Author

Mikaela commented Jan 2, 2024

Funnily RELAYMSG #/dev/null is fine though

slingamn added a commit to slingamn/ergo that referenced this issue Jan 3, 2024
@slingamn
fix ergochat#2114
6e56d2b 
Channels with slashes (or other relaymsg separators) in their names
were being falsely detected as relaymsg identifiers.
slingamn added a commit that referenced this issue Jan 4, 2024
@slingamn
Merge pull request #2115 from slingamn/issue2114_relaymsg
1d8bbde 
fix #2114
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Mikaela