-
Notifications
You must be signed in to change notification settings - Fork 36
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
Document PRIVMSG server mask #134
Conversation
See also ircdocs/wooooms#5 |
cc @progval: any chance to get this reviewed? |
cc @progval: does this look good to you? |
Sorry, I just need to test the existing impls first |
Note: there are some implementations that further restrict the format of the server mask specified, for example I have come accross an implementation where "$" was not allowed and a format such as "$.tld" was required instead |
I just checked support with various servers: Support So the behavior described in this PR only applies to Unreal and Insp. It could be amended to describe Unreal+Insp+ngirc+plexus4, but is it worth it? |
Oh also: servers that do support them send messages to all users on the server but the sender. And some servers rewrite the target (Insp always replaces it with |
ircdocs/modern-irc#134 A bunch of tests are failing, we need to work this out in the Modern PR Note: it needs the following patch to plexus4 to be relevant: ```diff diff --git a/modules/core/m_message.c b/modules/core/m_message.c index adf0821..7568f20 100644 --- a/modules/core/m_message.c +++ b/modules/core/m_message.c @@ -575,7 +575,7 @@ handle_special(int p_or_n, const char *command, struct Client *client_p, return; } - if (MyClient(source_p) && !HasUMode(source_p, UMODE_NETADMIN) && !HasFlag(source_p, FLAGS_SERVICE) && strcmp(nick + 1, me.name)) + if (false) { sendto_one(source_p, form_str(ERR_NOPRIVILEGES), me.name, source_p->name); return; ``` (I'm too lazy to figure out how to become a netadmin)
My main motivation is to add some notes in the spec to tell clients to handle these messages properly, ie. put them in the server buffer if applicable and don't open a new query buffer. Maybe we should only spec the receiving end of this: receiving a message starting with |
Sounds good. You could mention in passing what it's for.
Just mention it's a possibility, this should be up to the implementation |
c2f3119
to
2f7bada
Compare
Done! |
2f7bada
to
1208cfd
Compare
👍 |
No description provided.