-
Notifications
You must be signed in to change notification settings - Fork 85
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
Nickserv Nick registration and identify box #488
Comments
I agree this would be nice. But I guess if you set up an LDAP backend for both Convos and your NICKSERV than you would not have to register separately at all? |
Hmm, so I have been thinking about this a bit further... I guess the LDAP option would not work, as Convos has no way to tell the IRCd that it is the same account, so the nickname would conflict? Seems like right now it is a bit difficult to run a Convos instance that also allows people to be registered via Nickserv? |
I don't understand how LDAP is important. Wouldn't the information in "identify box" just be used as an on-connect-command? |
The question is: how to combine Convos accounts with those understood by Nickserv. I guess when using Convos with an external 3rd party IRCd service it doesn't really matter as you will have to have two separate accounts anyways (unless you can do some Oauth2 magic). But on services that want to combine a IRCd with Convos it would be great to have a way to combine the logins. |
The nickserv identify password should also be in a different input box in the connection settings, under "Authentication settings". The "Password" box might change name to "Server password" and the new box could be "Identify password (Nickserv)" or something like that. |
It would be really convenient for convos users to have a Nickserv nick registration box.
Also, if a user logins/changes nick to registered one, a box could pop up asking for the password instead of putting the command line for identification.
The text was updated successfully, but these errors were encountered: