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

channels may start with not just # and & but also + and ! #70

Open
timo opened this issue Sep 2, 2024 · 0 comments
Open

channels may start with not just # and & but also + and ! #70

timo opened this issue Sep 2, 2024 · 0 comments

Comments

@timo
Copy link

timo commented Sep 2, 2024

Randomly stumbled upon this while reading the source. This is the first line that uses # and & to check if a message is going to a channel, or if it's meant to be a private message to just the user:

$channel.starts-with('#') || $channel.starts-with('&')

There are a few more mentions.

Here's a section in the RFC2811 that names the allowed prefixes for channels:

https://datatracker.ietf.org/doc/html/rfc2811#section-3

In regard to the lifetime of a channel, there are typically two
groups of channels: standard channels which prefix is either '&', '#'
or '+', and "safe channels" which prefix is '!'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant