Comment 16 for bug 256478

Considering the bug has been open for just short of two years, and has at best a Wishlist state. The upstream report for this is nearly three years old. Yet somehow this has still been selected as the default client for Ubuntu. As others have pointed out this is a fairly standard feature of multi-network chat clients.

Couple this with the apparent complete lack of support for keyboard binds and I fail to see how this client was remotely ready to be selected as the default chat client. Especially in an LTS release. I'd say the noise is needed.