node-irc
node-irc copied to clipboard
martynsmith
NodeJS IRC client library
The 275 shows whether a client is connected using SSL.
The user modes inside "channel.users" structure was not being updated. The comparison wasn't returning the expected value, so I changed it a little. Now the user modes are being updated...
Any ideas why I keep seeing Client-EOF quit with the following in the logs: ``` ^[[35m[2015-01-10 11:02:12.788] [FATAL] p3negram - TypeError: Cannot read property 'key' of undefined at Client. (/home/munkee/Programs/NodeApps/node-p3negram/node_modules/irc/lib/irc.js:431:46)...
Many asian IRC servers support CJK characters in nicknames. From RFC2812(https://tools.ietf.org/html/rfc2812#section-2.3.1), nickname should be ``` nickname = ( letter / special ) *8( letter / digit / special / "-"...
Connecting on freenode.net, I get this warning : ``` Unhandled message: { prefix: 'barjavel.freenode.net', server: 'barjavel.freenode.net', command: 'rpl_luserunknown', rawCommand: '253', commandType: 'reply', args: [ 'HelloNodeBot', '3', 'unknown connection(s)' ] }...
http://ircv3.net/specs/core/message-tags-3.2.html Old syntax: ``` ::= [':' ] ``` New syntax: ``` ::= ['@' ] [':' ] ``` where ``` ::= [';' ]* ::= ['=' ] ::= [ '/' ] ::=...
Parse Twitch-specific message metadata. Twitch includes information such as color, name with capitalization and emote information alongside messages in a (AFAICT) non-standard way.
When I do Client.whois(nick, callback) the callback isn't executed. I do get reply via 'raw' event and 'whois' event (which is just { nick: nick }, useless).
## Scenario: 1. I do Client.join() with callback, supplying incorrect channel key 2. Then I realize, what've I done, and supply correct channel key ## Desired behavior: 1. Callback should...
ZNC uses the prefix `*[email protected]` for its messages but the `*status` nickname is not actually RFC conformant, which is what node-irc only accepts as a proper nickname in its parsing...
