Allow to set custom identify request message on Nickserv module #1611
Comments
|
That's why there is SASL: it's protocol which doesn't depend on the
language of the server. If server supports SASL, you can use sasl module
instead of nickserv module.
пт, 26 окт. 2018 г. в 14:57, Antonio Spadaro <notifications@github.com>:
… I'm actually connected to a non-english server. IRC OPs translated the
Nickserv identify request message and obviously ZNC doesn't recognize it.
Allowing people to set up a custom identify request message that will be
used to match Nickserv identify request will avoid issues like #588
<#588> and #364
<#364>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1611>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAT15FTbPEIeOxunjJGu0aid6aiqlZy0ks5uoxS5gaJpZM4X8SbZ>
.
|
|
Server doesn't support SASL. I had to recompile nickserv.cpp adding the identify request message I needed |
|
Since the nickserv module already supports configuring the messages it sends, I don't think it's too much to also support custom matching on inbound notices from services. I think I'll play with this, and send a PR if I get something working. |
|
It's also possible to use perform for NickServ identifying. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm actually connected to a non-english server. IRC OPs translated the Nickserv identify request message and obviously ZNC doesn't recognize it.
Allowing people to set up a custom identify request message that will be used to match Nickserv identify request will avoid issues like #588 and #364
The text was updated successfully, but these errors were encountered: