@bmillham, could you show me how to reproduce this, and on which network?
I tried the following on Libera:

Test 1

1. Halloy joins #FOObaz
2. Second client joins #foobaz
3. Second client sends "hi"
4. Halloy sees "hi"

Test 2

1. Second client joins #ROCKit
2. Halloy joins #rockit
3. Halloy sends "hi"
4. Second client sees "hi"

Libera (solanum) normalizes channel names. You can't reproduce the bug there.

Libera (solanum) normalizes channel names. You can't reproduce the bug there.

That explains. Thank you.

Hi @casperstorm
Tested on 2014.12 and on 825be98
I've encountered this bug too on russian ircnet.ru network.

If you connect to it via ircnet.ru:6688 server and join #usue channel - the channel you've joined will be #Usue and you will be able to see only messages from those who are connected to #Usue somehow but you'll see full users list.

If you connect to it via irc.386.ru:6688 server and join #usue channel - the channel you've joined will be #usue and you will be able to see only messages from those who are connected to #usue somehow but you'll see full users list.

With all other clients I've tried - there is no such behavior: every message from every user is seen on the channel. Must say it has confused me a lot from the start. But I do think it's connected with how Halloy treats case sensitivity. It joins the same channel butt somehow ignores some messages (the are not visible anywhere).

Been able to reproduce: while being connected through soju I've changed the network and ended up on 2 cchannels at the same time #usue and #Usue (which is the same channel actually).
If I write in #usue buffer - I don't see those messages in #Usue buffer. Same goes for some messages from some of the users on the channel.

Here is screenshot from gamja (which like all other clients doesn't have this problem)

Really like Halloy so I think something could be done. Because at the moment I'm unable to use it on some networks.

Will start looking into this next @gAlleb!

Thank you!

ircnet.ru doesn't use Solanum but historically uses PTlink (PTlink7.1.0-rc2). I'm not an expert but I assume that depending on the linked server inside this network it (the server) sends some kind of raw channel data that differs in cases (and those servers somehow store channel data with different cases due to unknown reasons - maybe from the point when a channel has been created on one server and then recreated with lower case on another). Maybe not.

Because when you are inside the network and you /join #usue (or /join #uSUe or /join #usUE ) - you end up either on #usue or #Usue depending on the server you are being connected to and (when using Halloy) will see only messages from the users that have the same channel name. But i'm glad that could catch this cause at the beginning I thought that I'm going mad when I've seen a person talking and talking to himself :)

We don't handle server casemapping settings which dictate how we should deal with case sensitivity / case conversion.

We need to handle this properly which will fix this issue

We need to handle this properly which will fix this issue

True. Looking forward. Thank you!

Also if it's possible, it would be really nice if you could share some thoughts and insights on the cause of this bug after the fix. For educational purposes :) Cause it's an interesting issue.

Same goes for user names sometimes:

I can reproduce this with soju - bouncerserv vs BouncerServ

This issue also affects users of the GeekShed network as their servers do not normalise capitalisation of channel names either.