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 https://github.com/znc/znc/issues/588 and https://github.com/znc/znc/issues/364
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 https://github.com/znc/znc/issues/588 and https://github.com/znc/znc/issues/364
<!-- github-sync-id:374395937 -->
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.
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 https://github.com/znc/znc/issues/588 and #364 https://github.com/znc/znc/issues/364
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
> <https://github.com/znc/znc/issues/588> and #364
> <https://github.com/znc/znc/issues/364>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/znc/znc/issues/1611>, or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAT15FTbPEIeOxunjJGu0aid6aiqlZy0ks5uoxS5gaJpZM4X8SbZ>
> .
>
<!-- github-comment-id:433443698 -->
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.
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.
<!-- github-comment-id:433542162 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 https://github.com/znc/znc/issues/588 and https://github.com/znc/znc/issues/364
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:
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.