Bug 16177 - Add NickServ/ChanServ support
Summary: Add NickServ/ChanServ support
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: idle (show other bugs)
Version: unspecified
Hardware: All All
: low enhancement
Assignee: Telepathy bugs list
QA Contact: Omer Akram
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-31 12:10 UTC by Florian Steinel
Modified: 2019-12-03 19:24 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Florian Steinel 2008-05-31 12:10:18 UTC
Add Support for NickServ/ChanServ.
NickServ:
- Register User (Password)
- get additional Info for users (Email, Website, etc.)

IRC NickServ/ChanServ sourcecode:
- http://www.anope.org/
- http://www.google.com/codesearch?q=nickserv
Comment 1 Simon McVittie 2009-07-20 06:18:57 UTC
Low priority. Let's walk before we try to run :-)

Some of these things don't necessarily have a Telepathy API yet, and I suspect they all rely on the ability to recognise particular IRC networks and behave suitably.
Comment 2 Will Thompson 2009-11-04 09:53:13 UTC
Note that at least Freenode treats the server password, if set, as your NickServ password, so you may be able to work around this for now.
Comment 3 Michael 2010-04-08 02:27:10 UTC
Does it make sense to generally send the IRC password to the nick server?  I seem to recall that Konversation does this.  That might simplify fixing this :)
Comment 4 Omer Akram 2010-04-08 04:00:06 UTC
Also reported at: https://bugs.launchpad.net/ubuntu/+source/telepathy-idle/+bug/557119
Comment 5 Simon McVittie 2010-04-08 05:37:01 UTC
(In reply to comment #3)
> Does it make sense to generally send the IRC password to the nick server?  I
> seem to recall that Konversation does this.  That might simplify fixing this :)

Only on networks where there identifiably *is* a nick server (if a malicious user joins a network that doesn't have a nickserv and calls themselves nickserv, you don't want to send *them* your password!), which brings us back to the problem of identifying which network you're on. If Konversation has code for this, perhaps it could be adapted.
Comment 6 Michael 2010-04-08 07:46:38 UTC
No, I double checked and Konversation - at least in the current version - does require you to explicitly configure a nick and a password for auto-identifying.  Perhaps my memory serves me false.
Comment 7 Florian Steinel 2010-04-08 10:36:55 UTC
On freenode.net the password login work.
With oftc.net net-irc/telepathy-idle-0.1.5 fails to autologin.
Oftc only supports "Automatically Identifying Using SSL + CertFP" and as fallback "nickserv identify".
http://www.oftc.net/oftc/NickServ/CertFP
Comment 8 Michael 2010-04-09 01:59:09 UTC
freenode forwards your IRC server password to the nickserv.  This is a feature of freenode, and is arguably much better than auto-identifying with the nickserv, but sadly other servers don't do this.  Just for the sake of the argument though, is this really better in telepathy-idle than in Empathy?  My understanding was that telepathy-idle was mainly there for providing the mechanisms and Empathy the interface, but the auto-identify hack makes use of mechanisms that are already present in telepathy-idle (basically /msg).

For the record, XChat also has a separate "nickserv password" field in its configuration, but doesn't let you specify an alternative nick for nickserv like Konversation does.  Don't know if that is really necessary anyway.
Comment 9 GitLab Migration User 2019-12-03 19:24:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-idle/issues/3.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.