Quassel client windows

You signed out in another tab or window. Want a really cool IRC client? Then follow these EZPZ steps! Install it. Head over to this Gist and copy all the text. Set the checkboxes as you see in the below images. Now that you have done that, those lists should appear in your client, but probably not in the best places. You can launch quassel-webserver in http mode by adding -m http to the command line.

This tells the webserver to run in http mode, and to listen on port This way you can let your apache or nginx server handle the SSL layer. Also, be sure to launch quassel-webserver in http mode by adding -m http to the command line, optionally including -l localhost to block direct outside connections from bypassing the proxy server. This is a known issue but there is a workaround:.

It means that quassel-webserver has been killed prematurely. Skip to content. Star Branches Tags. Could not load branches. Could not load tags. Latest commit. Upon opening Nettalk for the first time, open the connection window click the top left icon with a green plus sign.

Click next and choose your nickname, then click next again. Click complete. This will let you simply double-click on that "chat" to open the IRC chat, just as you would start a conversation with a standard user on other chat protocols in Pidgin by double-clicking on their username. Note: A single buddy can only link to a single channel Click "Add" and that channel will now appear as a "chat" on your list that you can open at any time. These instructions apply to the free and open source Quassel IRC client.

On the top half of the window, choose the "Add Choose the "Manually specify network settings" radio button, and choose the following manual settings:. You can leave the server password blank.

Add "twitlive" no quotes in the Channel window and press OK. See below for even more disclaimers. Our main repository is located at Github. Contributions are very welcome, and preferred in the form of pull requests on Github. The code you get from this repository is not intended for productive use.

We sometimes break things or commit experimental features. However, we do try to keep the master branch in a usable and compiling state most of the time, as we have many users building from that despite all our disclaimers ;- Breakages usually get reported very quickly.

Please note however that we might upgrade configuration files or the database scheme without prior notice, and you may not be able to run older versions afterwards, as we don't support downgrades. You have been warned!