Unable to identify with NickServ (freenode) in bouncer mode

[casperploug]

Setup

Chrome 22.0.1229.79

Server: chat.freenode.org:7000 with SSL. Bouncer mode enabled.

Procedure

Upon connecting with reserved nick, an unregistered event is sent:
... "command":"err_notregistered","rawCommand":"451","commandType":"error","args":["*","You have not registered"]}}]}

Issuing a /msg NickServ adds a NickServ tab in the left sidebar, but it is not clickable (you remain in the status window). The authentication doesn't seem to be sent either, and shortly after Subway tries to reconnect, again and again.

Comments

Based on debug information, Subway does seem to register that I'm trying to send that message:

   debug - websocket writing 5:::{"name":"oldMessages","args":[{"name":"nickserv","messages":[{"channel":"nickserv","server":"chat.freenode.org","linkedto":"casper","message":"identify <my pass>","_id":"506ed6c13cb5071b13000007","date":"2012-10-05T12:46:57.713Z"}]}]}

davidcollantes seems to have a similar issue as noted on Show HN: Subway, a persistent web client for IRC. The post is rather old by now, but the NickServ complication is still there.

I was unable to find a related issue, here on GitHub, so perhabs I'm using it wrong. It seems like an obvious first thing users of Subway needs. The main screenshot on the repo also depicts freenode, so I'd be surprised if the NickServ issue was discovered by me.

This only happens when bouncer mode is enabled.

If anyone can confirm that this is a common issue, I'd be happy to investigate and work on a patch for submission.