IRCds generally have IRCd-side aliases NICKSERV and CHANSERV which check that the service in question is U-lined and not someone who has gotten the nick thanks to service misconfiguration (which has happened also on freenode) and it would be nice especially with NICKSERV as it forwards the password, but would possibly allow accessing ChanServ faster.
What I suggest is allowing !nickserv identify foo bar in the admin room and have the ghost send NICKSERV identify foo bar to the IRCd instead of having to open a direct chat with NickServ.
With ChanServ in some cases it would be faster to !chanserv quiet #channel troll than having to open a direct chat with ChanServ and I think these two aliases are the most often used.
kegsay
commented
7 years ago
IRCds generally have IRCd-side aliases NICKSERV and CHANSERV which check that the service in question is U-lined and not someone who has gotten the nick thanks to service misconfiguration (which has happened also on freenode) and it would be nice especially with NICKSERV as it forwards the password, but would possibly allow accessing ChanServ faster.
What I suggest is allowing
!nickserv identify foo barin the admin room and have the ghost sendNICKSERV identify foo barto the IRCd instead of having to open a direct chat with NickServ.With ChanServ in some cases it would be faster to
!chanserv quiet #channel trollthan having to open a direct chat with ChanServ and I think these two aliases are the most often used.