QuasselWiki » History » Version 69

Version 68 (dalbers, 12/15/2009 10:36 PM) → Version 69/216 (tan, 12/30/2009 12:31 AM)

h1. Quassel


h2. Introduction

Quassel is a program to connect to an IRC network. It has the unique ability to split the graphical component (quasselclient) from the part that handles the IRC connection (quasselcore). This means that you can have a remote core permanently connected to one or more IRC networks and attach a client from wherever you are without moving around any information or settings. However, Quassel can easily behave like any other client by combining them into one binary, which is referred to as "Quassel Mono".

Quassel's distributed approach:


In simpler terms, the "monolithic" client is a response to requests for a client that behaves like every other IRC client. The monolithic client (GUI) is what makes the connections to the IRC networks. In normal operation, the client (GUI) connnects to a core, it is completely incapable of connecting to anything else. The core recieves connections from clients, and makes connections to the IRC networks, it also handles logging (currently everything gets put in the database).

h2. Getting started

Setting up Quassel is fairly easy and straightforward. Since we have a separated core and client, we will configure them in two steps. If you are using the Quassel Mono version, then you can skip the core part as this is done internally.

h3. Installation

The best and most reliable way is to simply install the packages provided by your distribution. However, we do offer some static binaries at along with Git instructions for those who prefer to compile Quassel themselves.

h3. Specific installation instructions

* [[Build Quassel on Windows]]
* [[Build Quassel on Linux (english)]]
* [[Build Quassel on Linux (deutsch)]]
* [[Build Core On Ubuntu]]: Setting up Quassel core from the source code on Ubuntu server (mostly applies to Debian too)
* [[Building quasselcore on Ubuntu 8.04 Hardy Heron/x64 (old Qt4 libs)]]

h3. Connecting to the core

Before starting the core, you could set up [[Client-Core SSL support|Client-Core SSL encryption]] or have a look at the [[PostgreSQL|PostgreSQL article]] before moving on.
All that is completely optional.

Now start the core and launch quasselclient on your local machine. A connection dialog will show up. Enter the IP address or hostname of the server running the core, enter the port number used by the core and select SSL if applicable. You can also specify a proxy but note that domain names will still be resolved locally (see "Qt4.4":

During the first connection, you will be guided through a graphical wizard to configure the core properly. Enter a username and password, this will be the administrator. Next, select a database backend (for now this is SQLite only). Click finish and your core is ready!

A configuration screen for adding new users and managing existing ones is under developement, but for the time being you can use a simple [[Manage core users|python script]].

h3. IRC Configuration

Now you have to specify which network(s) Quassel should connect to. First you will have to create an identity.


Set a real name (which doesn't actually have to be real) and add the nicknames you want to use. If the first nickname is not available, the second one (if specified) will be used instead. Change the other settings if you like, this is optional however.

After creating an identity, you have to define the IRC network(s) along with the servers they use. If Quassel was installed properly, there should be a preconfigured list of the most popular networks already.


Make sure you select the identity you just created (which should be the default). Click OK and you're done. Feel free to visit us in the #quassel channel on Freenode!

h2. Manuals

* [[Manage core users]]
* [[Buffer Views]]
* [[Quassel Logging]]
* [[PostgreSQL]]: Setting up PostgreSQL database backend
* [[SQLite]]: Some information about the SQLite backend
* [[Client-Core SSL support]]: How to encrypt the connection between clients and core
* more [[Shortcuts]]

h2. Frequently asked questions

Check the [[FAQ]]

h2. Known issues

* DCC chat and file transfers are not yet supported.
* There has been a client for mobile devices but as the codebase updated so quickly it has become outdated and incompatible with newer cores.
* See "Issues": for specific bugs and feature requests.

h2. Translation and git patches

Translation now uses .po-files and the best way to send in updates to these is by git patches.
[[Creating Translation git patches]]: Here you can find out how to create those git patches.

Static builds and build instructions

* "Datafreak's Build for Windows": (required "MSVC Redistributable Package":
* "Phon's Build for Windows": (required "MSVC Redistributable Package": , SSL will not work.)
* "m4yer's Builds for Mac OSX 10.6 and 10.5":