Quassel IRC is a modern, cross-platform, distributed IRC client, meaning that one (or multiple) client(s) can attach to and detach from a central core -- much like the popular combination of screen and a text-based IRC client such as WeeChat, but graphical. In addition to this unique feature, we aim to bring a pleasurable, comfortable chatting experience to all major platforms (including Linux®, Windows®, and MacOS X® as well as Android smartphones), making communication with your peers not only convenient, but also ubiquitous available.
And the best of all: It's free - as in beer and as in speech, since we distribute Quassel under the GPL, and you are welcome to download and see for yourself!

Blogs

We Have Mailing Lists!

Hi all,

finally (after years of pushing and prodding for it), we now have mailing lists for Quassel IRC.
While most of user support and discussions happens in our IRC channels (mostly #quassel on
Freenode), mailing lists have distinct advantages - in particular, there is an archive, and
people can chime in asynchronously.

So now we offer the following lists:

  • quassel-announce

    This is a read-only list, where the development team will send important announcements
    to. We highly recommend distro packagers to subscribe to this one, as we'll announce
    releases and other important information there.

  • quassel-users

    This list should be used for general user discussion about and around Quassel IRC -
    questions, tips & tricks, that sort of things.

  • quassel-devel

    This list is for discussion about development of Quassel IRC itself. Everything that is related
    to development should go there, and we'll share our plans and ideas there as well.

So, feel free to go ahead and subscribe!

Please note that this is my first time setting up a list server, so if the lists show unexpected
behavior or have configuration issues, feel free to poke me so I can fix it.

~ Sput

Mandatory Upgrade: Quassel 0.9.1

TL;DR: If you're running Quassel Core or the stand-alone, monolithic client with Qt 4.8.5+ and PostgreSQL, you need to upgrade immediately!

Looks like Qt changed the string escaping rules in their PostgreSQL driver for Qt 4.8.5, which unfortunately may cause database corruption or data loss if you're running Quassel Core or the monolithic client with a PostgreSQL database and that Qt version. Older versions of Qt are safe, as are the pre-built packages for Windows, MacOSX and the static core from our website. All other users (and distros!) should upgrade their core or monolithic build to the brand-new 0.9.1 version of Quassel immediately. Thanks in particular to Tucos and brot for finding that issue and its cause!

In addition to the fix for this issue, a number of other fixes went into this release, most notably several ones related to key handling for encrypted channels. Also, you should now see Quassel come up in your preferred UI language on MacOSX again (rather than in Japanese).

Note that because of the urgent nature of this release, we couldn't wait with the announcement until binary packages for 0.9.1 have been provided. Those will be added in the next few days.

That's it for now. Over and out.
~ Sput

Onwards and Upwards - Quassel 0.9.0!

Yes, yes, I know. Again I have been too quiet on this page, while several major changes have happened in my real life. However, things are slowly settling down, and I could spend more time on Quassel again during the past few months. And as usual, the community has been active as well providing patches, fixes and features - thank you all for that!

So without further ado, I present to you Quassel 0.9.0!

A list of the most important changes can be found in the freshly updated ChangeLog - improved certificate handling, improved OSX support, DockManager compatibility, channel-specific highlights just to name a few features that have been contributed by the community (special thanks goes out to Tucos, who is restless indeed).

Meanwhile, I am slowly continuing to refactor the heart of Quassel, which is the communication between the client and the core. My goal is to abstract the protocol, so in the future it will be easier to write third-party clients. Having a clean protocol abstraction is also a prerequisite for getting things like events and scripting going. Expect more news along those lines in the future!

Oh, we've also switched to GitHub as primary means for source code hosting and managing contributions. The main reason for this is that people were unhappy with Gitorious because it was slow, sometimes unreliable, and has a less advanced web interface. So please, if you like to send patches, use pull requests on GitHub - that way, we'll make sure they won't get lost.

For translations, please continue to use Transifex.

And that's it, I think. Thank you all for your patience and continued support of Quassel, and have fun with the new release!

~ Sput

We are back - with Quassel 0.8.0

Has been a while that this page has seen updates, as we, the main developers, are still too busy with real life to get as much done as we would like. So many plans, so little time...

Thankfully, we have some pretty awesome guys from the community (al, Tucos, johu, kode54, Fish-Face, to name but a few) who help out not only with support in our IRC channel, but also with triaging bugs, and especially with sending patches. So we finally managed to clean out our merge request queue and got a new feature release going!

Quassel 0.8.0 brings you the usual slew of bugfixes, a ton of new languages and additional translations for the existing ones, and a few new features such as syslog support, configurable tab completion key, improved desktop integration and more.

Behind the scenes, and hopefully not noticeable for you, we've merged the new event backend into the core. This is more or less a complete rewrite of how the IRC protocol is handled, and the first major step towards full scripting support!

So don't hesitate to grab the new release and get rollin'!

A note for packagers: The Qt 4.8 release introduced an issue with QTreeView handling that causes parts of the nick list (and sometimes the chat lists) not being shown sometimes. For distributions that don't believe in frequent feature upgrades, we've rolled a 0.7.4 release that only contains this and some other bugfixes, but does not introduce new strings or features. If your distribution backports Qt 4.8, we warmly recommend backporting this version of Quassel as well!

That's all.
~ Sput

Quassel IRC v0.7.3

On September 8th, the IRC was in turmoil because someone discovered and actively exploited a bug in Quassel's CTCP handling that would cause the core to crash when processing a specially crafted CTCP message. What followed was masses of users quitting from Freenode, because their cores crashed.

We found and fixed the issue within a few hours, and have issued a new bugfix release. We strongly recommend updating your core or monolithic client as soon as possible to avoid crashes. Client-only builds are not affected.

Tarball and static core are available from the download page; some distros have already bumped their packages, others should follow soon. Packages for other platforms are not done yet, they will follow shortly.

If you cannot update your core right now, you (this means, all users of your core) should add an ignore rule to globally ignore CTCP requests. This will avoid the crash as well.

Sorry for the noise, but bugfree code is a myth :)

~ Sputnick

The State of Quassel (or: Why Are There No Updates?)

Because people keep wondering why our repository has been rather... quiet for the past few months, and not everybody finds his way into our IRC channel to ask us in person what's up, I think it's a good idea to finally blog about this.

I can assure everyone that the project isn't dead or anything. But the main developers are currently quite busy with real life, mainly with thesis writing, and Quassel development needs to suffer for that for the next few months. We intend to get back to development full steam once these rather time-consuming commitments have been dealt with, and we still have some cool plans in store to make Quassel an even better client once we're back!

In other news, we did package up 0.7.2 quite a while ago, but we're still waiting for Windows builds, so it's not up on the download page yet. You can get the tarball at the usual location though, and also find packages for Mac and the static core in the download dir. Some distros (Gentoo, *buntu) have already been shipping 0.7.2 packages for a while as well.

In even further news, some exceptionally cool things are being done by some of our users. For one, there is a native (!) Quassel client for Android devices under development. QuasselDroid is still work in progress, but I'm told it's shaping up really nicely.
For Maemo/MeeGo devices, Sandro Giessl is working on Quassel2Go, which at present is a version of the standard client modified for small touchscreens. We intend to merge this into the upstream codebase at some point in the future, but for now he maintains his own fork.

That's it for now. Stay tuned, while I go back to my thesis writing, and rest assured that Quassel will see more development again in just a few months!

The Lucky (minor) Number -- Releasing Quassel IRC v0.7.1

It's that time of the year when we're releasing a new Quassel, and this time we strongly recommend updating your core or monolithic client at least, as in older versions there was an issue with CTCP handling that might allow bad and ugly people to make your core unresponsive. This issue is also the reason for the 0.7.0 release being officially skipped. People still on 0.6.x and not wanting to update to a new feature release should upgrade to version 0.6.3 in which this issue is fixed as well.

Now read on for a short list of the major new features the 0.7 flavour gives you, besides a ton of bugfixes and translation improvements!

Requiring Qt 4.6

In a few days, the master branch (which will become quassel-0.7) will start depending on Qt 4.6 for the client only. Besides giving us some very welcome API additions, and fixing a few bugs we currently have to work around, this also allows us to use Qt Kinetic and the Animation Framework in the future.

Qt 4.6 has been released about half a year ago, and is also required by the current stable KDE release, so we think that most desktop distros should be up to par by now (or don't care enough about staying up-to-date, in which case they shouldn't be expected to ship a bleeding edge Quassel anyway). By the time quassel-0.7 is released, even more time will have gone by (and the next stable Qt release should be out).

The core's dep will remain at Qt 4.4.0 for now, so people running Debian Stable on their server should be ok. The deps for the current stable release 0.6.x won't be changed, so subsequent 0.6.x releases will still be fine with Qt 4.4 for the core and Qt 4.5 for the client.

YANT (Yet Another Note for Translators)

After doing some more experimenting with translation workflows, our Master of Translation Daniel "al" Albers has agreed to support Transifex as an additional means to create and maintain translations for Quassel. Thus, people not having or wanting a Launchpad account can use the Transifex portal for contributing translations now!

Since we're not dependending on Ubuntu downstream for managing the translations at Transifex, we are a bit more flexible when it comes to working with contributors, and we can sync the codebase with it more easily and more often. Please do check the other system though before starting, in order to not needlessly duplicating work.

al will integrate translations from both systems into Quassel, so we're not abandoning Launchpad/Rosetta, just providing an alternative.

In short, you can now use the following two frontends for helping Quassel be international:

Transifex - the open translation platform
Launchpad/Rosetta - Ubuntu Translators

Thanks for listening again, and I'm looking forward to seeing our po/ folder fill up! ;-)
~ Sputnick

Bumping Quassel: 0.6.1

It's that time of the year again, when we proudly do a new feature release of Quassel IRC! You might wonder why we've skipped the announcement for 0.6.0, though. The reason for this is that shortly after tagging, we've discovered two serious bugs in that version. One could make the monolithic client try to select the PostgreSQL backend rather than SQlite; the other would lead to a crash on startup in some setups. Since we usually let some days pass between tagging and announcing a release, those bugs were found and fixed before we'd officially released 0.6.0. Two days later, we tagged 0.6.1.

There are several major features in this release:

  • Completely reworked client/core connection featuring the long-awaited reconnection and Solid support as well as a streamlined UI
  • Support for the new DBus-based system tray of KDE and, in some distros, Gnome (StatusNotifier spec)
  • Improved notification handling
  • Support for inputting formatted (colored/bold/...) text
  • SASL auth support (replaces NickServ e.g. in Freenode)
  • Several new languages and improved translations for alreay existing ones
  • Build system improvements

See the ChangeLog for a more exhausting list of new features. Of course, we've also fixed many bugs and optimized some things in this release ;-)

As usual, we'll maintain the 0.6.x branch in feature and string freeze at least until 0.7.0 is released. This means that we'll backport bugfixes where it makes sense, but don't introduce new stuff in 0.6.x versions, in order to make packagers of freeze-loving distros happy.

Now go and grab this latest release of your favorite IRC client!

~ Sputnick

Syndicate content