Identifing with Nickserv/Q

[Platypuschan]

Is it possible to add "!storepassQ" to the command bot? so while not empty, it tries to auth to aganist Q instead of NickServ automatically? or is there a way to send "!cmd irc.quakenet.org PRIVMSG Q@CServe.quakenet.org :AUTH " after a reconnect?

[Half-Shot]

!storepass uses PASS, rather than sending anything automatically. I don't really want to add any NickServ specific functionality into the bridge, ideally.

[Platypuschan]

for some servers (i.e. irc.dal.net) it seems broken... i can´t talk to nickserv with a msg, i have to send it with !cmd irc.dal.net PRIVMSG NickServ@services.dal.net :IDENTIFY <password> manually after each reconnect. Maybe just some some option to auto-send some commands after a connection would solve this...

[jgoerzen]

@Half-Shot This tripped me up with OFTC. It, as well as many other networks, do not accept a Nickserv password in PASS. Both the guides at https://github.com/matrix-org/matrix-appservice-irc/wiki/Guide:-How-to-use-Matrix-to-participate-in-IRC-rooms and at https://github.com/matrix-org/matrix-appservice-irc/wiki/End-user-FAQ imply differently.

In fact, the latter, there is a section on "How to register/identify with NickServ" followed by a section on "how to do it automatically" which says it is "sent as a PASS command to NickServ."

I think actually, rather than using PASS, it should use the PRIVMSG version of /msg nickserv identify pass everywhere. This PASS business is not supported on most networks as far as I am aware.

[jgoerzen]

I am probably going to have to run my own OFTC IRC bridge via ZNC because of this. I join some channels that require registration, and every time either the IRC node or the Matrix node restarts, I'll lose them.

[DemiMarie]

@Half-Shot Implementing NickServ specific functionality seems to be a real-world requirement in practice.

[gegoxaren]

Quakenet does not use NickServ, it uses Q. Q can only be authed on via /msg Q@CServe.quakenet.org AUTH.

The ideal solution would be to have bridge configurable rules per network.

How exactly the rules are to be stored is something that needs to be discussed.

Maybe something along the lines of this:

{
    "irc.examplenetwork.net" : {
        {
            "auth_bot" : "Auth@secure.examplenetwork.net",
            "message" : "AUTH $username $password", 
            "pass_only_message" : "AUTH $password", 
        }, 
    },
   "irc.libera.chat" : { .... }, 
} 

The $password and $username would be replaced at when a request is done.

This would make the problems with networks that have other orders of nicks/pass pairs easier to handle.