You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When someone joins #channel and types something, that message is correctly handled by the listener. However, if someone joins #Channel or #cHannEL, etc (with caps in it, it directs them to same room), but the Listener won't even notice their message. Most IRC clients I believe correct the channel room name for their clients; however, I noticed specifically with mibbit web irc client that it doesn't--So I'm not sure if there are other clients out there as well that could fail to do this. Either way, is there a way to correct this in the node-irc lib?
The text was updated successfully, but these errors were encountered:
I personally haven't used the message#channel listener yet, but I have noticed that issue. Though I am currently unaware of any case-sensitive networks, I didn't want to change the library just in case one does exist. My workaround was to display the target (channel or nick) name to the user as typed, but, in the client, convert all message targets to lowercase before determining where on the page or whether to display it.
Thanks for the reply qsheets. I think I've figured it out. If I keep the #channel lowercase it won't run into those issues. Its when I type the channel as #Channel that it has those issues. So message#channel will recognize #Chanel and #chaNNEl and #channel. But message#Channel will just recognize #Channel.
Just came across this lil bug. I have:
client.addListener("message#channel", function(){};
When someone joins #channel and types something, that message is correctly handled by the listener. However, if someone joins #Channel or #cHannEL, etc (with caps in it, it directs them to same room), but the Listener won't even notice their message. Most IRC clients I believe correct the channel room name for their clients; however, I noticed specifically with mibbit web irc client that it doesn't--So I'm not sure if there are other clients out there as well that could fail to do this. Either way, is there a way to correct this in the node-irc lib?
The text was updated successfully, but these errors were encountered: