Skip to content
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

Automatic NickServ /IDENTIFYcation? #47

Closed
Hello71 opened this issue Oct 27, 2011 · 6 comments
Closed

Automatic NickServ /IDENTIFYcation? #47

Hello71 opened this issue Oct 27, 2011 · 6 comments

Comments

@Hello71
Copy link
Contributor

Hello71 commented Oct 27, 2011

Also, join channels only after NickServ acknowledges identification; many networks use cloaks which are only enabled after NickServ is identified to.

@martynsmith
Copy link
Owner

I'm not sure this functionality really belongs in an IRC client library.

If anything it should be some sort of plugin for the library ...

@fent
Copy link
Contributor

fent commented Nov 3, 2011

I agree with martyn, it doesn't belong in the core irc library. But I've been working on a module to do just this,
https://github.com/fent/nickserv

Still in development because the nickserv service does not have a strict protocal that everyone follows, and so it's different with different software.

@Hello71
Copy link
Contributor Author

Hello71 commented Nov 3, 2011

Somewhat OT, but why is irc only a devDependency?

On 11-11-03 10:23 AM, Roly Fentanes wrote:

I agree with martyn, it doesn't belong in the core irc library. But I've been working on a module to do just this,
https://github.com/fent/nickserv

Still in development because the nickserv service does not have a strict protocal that everyone follows, and so it's different with different software.


Reply to this email directly or view it on GitHub:
#47 (comment)

@Hello71
Copy link
Contributor Author

Hello71 commented Nov 3, 2011

Also, I've only seen one "standard" method:

 /msg NickServ IDENTIFY *password*

Of course, many networks have implemented shortcuts:

 /nickserv IDENTIFY *password*
 /ns IDENTIFY *password*
 /identify *password*
 /id *password*

Or, my favorite, having it in client registration as a password in PASS.

On 11-11-03 10:23 AM, Roly Fentanes wrote:

I agree with martyn, it doesn't belong in the core irc library. But I've been working on a module to do just this,
https://github.com/fent/nickserv

Still in development because the nickserv service does not have a strict protocal that everyone follows, and so it's different with different software.


Reply to this email directly or view it on GitHub:
#47 (comment)

@fent
Copy link
Contributor

fent commented Nov 3, 2011

irc is a devDependency because the irc library is used to test, but it doesn't get required in the module.

/nickserv [command] seems to be universal. There are some commands that don't exist in some nickserv software, but what's the most troubling is that every one of them seems to have a different response to every command. If you want to join a channel only after you are successfully identified, then to know the module needs to look at the response.

@martynsmith
Copy link
Owner

Yes, and I know that the services I'm running on my own IRC server use

/msg authserv auth [username] [password]

which is completely different ;-) (I believe that's how Undernet works).

I'm going to close this Issue for now.

If someone wanted to create some sort of pluggable system to provide network-specific functionality then I'd happily consider merging it :-)

Half-Shot referenced this issue in matrix-org/node-irc Feb 23, 2019
Fixes #47.

Per https://www.alien.net.au/irc/irc2numerics.html, it has a conflicting
definition with aircd, but aircd (as noted previously) doesn't seem to
be in major use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants