According to RFC 2812, the maximum nickname length is 9, but this is actually determined by the server.
In IRCSock.cpp, "m_uMaxNickLen = 9;" should be configurable.
According to RFC 2812, the maximum nickname length is 9, but this is actually determined by the server.
In IRCSock.cpp, "m_uMaxNickLen = 9;" should be configurable.
<!-- github-sync-id:24847602 -->
You forgot the "Why?". ZNC reads the NICKLEN from 005 (ISUPPORT). Thus, that hardcoded 9 only matters while trying to establish a connection and there it seems to be only used in SendAltNick(). This function is used to find a new nick when we get a "nickname already in use" reply while connecting.
I can live fine with nicknames being truncated in this one corner case...
You forgot the "Why?". ZNC reads the NICKLEN from 005 (ISUPPORT). Thus, that hardcoded 9 only matters while trying to establish a connection and there it seems to be only used in SendAltNick(). This function is used to find a new nick when we get a "nickname already in use" reply while connecting.
I can live fine with nicknames being truncated in this one corner case...
<!-- github-comment-id:31300202 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
According to RFC 2812, the maximum nickname length is 9, but this is actually determined by the server.
In IRCSock.cpp, "m_uMaxNickLen = 9;" should be configurable.
You forgot the "Why?". ZNC reads the NICKLEN from 005 (ISUPPORT). Thus, that hardcoded 9 only matters while trying to establish a connection and there it seems to be only used in SendAltNick(). This function is used to find a new nick when we get a "nickname already in use" reply while connecting.
I can live fine with nicknames being truncated in this one corner case...