search

indrora / Atomic

Atomic: an IRC client from the ashes of yaaic
https://indrora.github.io/Atomic/
GNU General Public License v3.0
124 stars 29 forks source link

Onconnect nickserv authentication fails #61

Closed undu closed 9 years ago

undu commented 9 years ago

Whenever Atomic connects to the tawx network it sends the identify command, nickserv responds with the message "You have not registered" and finally nickserv changes my nick because I'm using a registered nick but haven't issued an identify command.

Here's a screenshot of the server screen with the unexpected behaviour: Screenshot

One way to get around this would be investigate on why it fails and implement correct behaviour (maybe it's sending the command before it should?), another would be recognizing that the login has actually failed and retry at a later time.

I'm using version 1.18 from f-droid.

indrora commented 9 years ago

Fixed in 37f297ca1891aca791febcc3b7a30e89a7415cb8

mark-orion commented 9 years ago

I am also using atomic from f-droid repo: Version 1.19 has this bug, so I had to downgrade to 1.18 in order to use NickServ again.

indrora commented 9 years ago

I can't reproduce this bug across multiple servers reliably. I've tested it against a handful of networks I'm registered and they all want a slightly different NickServ connection mechanism.

It looks like the problem (and I may be wrong here) is that each IRC network wants different ways of talking to services. Some want you to send the line NICKSERV IDENTIFY <password> while others want you to send PRIVMSG NICKSERV IDENTIFY <nickname> <password>. DALNet doesn't even use that, instead you message nickserv@services.dal.net and THAT doesn't even always seem to be consistent.

If this doesn't work for you, add the appropriate line to the commands sent on connection.