When I start a private chat (query) with a user whose nickname uses uppercase letters, the query will have the name lowercased. E.g. a query to NickServ will have nickserv as title.
Impacts
This is at first only annoying because I recognize my contacts also in exact writing, and even if IRC does not distinguish between lower und upper case, it is not what I expect.
The second effect is worse: I use ZNC as bouncer which keeps logs from conversations on the server. When I start e.g. a query with NickServ, ZNC creates a file NickServ_[date].log where all messages from NickServ are logged. But since Atomic starts indeed a conversation with nickserv, ZNC also creates a file nickserv[date].log where just my messages are logged. So the conversation is split into two files, where normally it’s just the one file `NickServ[date].log`.
Comments on the bug
It looks to me as if Atomic forcefully lowercases the nickname for queries (because it is written correctly in the user’s list), which is unnecessary and leads to other bugs as described above.
Description and steps to reproduce
When I start a private chat (query) with a user whose nickname uses uppercase letters, the query will have the name lowercased. E.g. a query to NickServ will have nickserv as title.
Impacts
This is at first only annoying because I recognize my contacts also in exact writing, and even if IRC does not distinguish between lower und upper case, it is not what I expect.
The second effect is worse: I use ZNC as bouncer which keeps logs from conversations on the server. When I start e.g. a query with NickServ, ZNC creates a file NickServ_[date].log where all messages from NickServ are logged. But since Atomic starts indeed a conversation with nickserv, ZNC also creates a file nickserv[date].log where just my messages are logged. So the conversation is split into two files, where normally it’s just the one file `NickServ[date].log`.
Comments on the bug
It looks to me as if Atomic forcefully lowercases the nickname for queries (because it is written correctly in the user’s list), which is unnecessary and leads to other bugs as described above.