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

Urgent: Security Upgrade!

Well, looks like 0.3.0.2 was not the last 0.3.0 release after all. coekie found an issue with CTCP handling in Quassel Core that allows attackers to send arbitrary IRC messages on your behalf. This issue is present in all versions prior to 0.3.0.3 and Git older than October 26th (rev. d7a0381).

This has been fixed in the quassel-0.3.0.3 release and also in Git and the nightly builds. Gentoo and *buntu already ship the new version, with more distributions hopefully following ASAP. If you still use a 0.2-rc1 core, please consider updating to 0.3.x as soon as possible. Note that we provide unstable, but fixed packages for Debian now, thanks to dileX.

Note that this affects (only) the core, so you'll need to update and restart your core. Clients are not affected. Also, this exploit can not be used to affect anything on your system, including your local account, as it is purely IRC related.

We are sorry for any inconvenience this causes to you, and hope this first will also be our last security fix for a long time to come...

What I took away from Munich

The Quassel development team (yes, in full force) has been at the Trolltech Qt Developer Days in Munich again. As last year, Trolltech Nokia has generously invited us to the conference in the shiny Hilton hotel. We had a great time, met a lot of interesting people and saw several interesting talks. Our thanks go in particular to Knut Yrvin, Qt Software's community manager, for making this possible.

A few random points I took away from that event:

Finalizing 0.3.0

Most people visiting our channel #quassel at Freenode already know that we have tagged the supposedly last bugfix release for the 0.3.0 branch a couple weeks ago. We have shied away from publicly announcing the release since we usually want to have binaries for all platforms ready first. Anyway, since our Linux buildbox is going to be out of service for at least a few more weeks, we are now officially releasing quassel-0.3.0.2, available on our download page!

This release only contains the remaining bugfixes based on 0.3.0. Compared to 0.3.0.1, these are some build system fixes and an issue with the topic widget. There are no new features, as 0.3.0.x expressly is a bugfix branch.

Windows users can be happy, since we now provide a monolithic client again! This means, those of you running a local core can now use the more convenient integrated binary again.
On the other hand, Linux users won't find a static core, but the one from 0.3.0.1 hasn't changed anyway...

Assuming no real blockers surface in the future, this release marks the end of supporting 0.3.0. We are concentrating on getting shiny new features into trunk and the upcoming 0.3.1 release instead :)

Fan Mail

So a couple days ago, I had a nice surprise in my mailbox:

Nice finnish vodka

Sent by jussi01 all the way from Finland to Germany, as a huge Thank You for the development team :) Needless to say that, while it might not increase productivity at our next devmeeting, it surely increases the dev team's motivation to continue to make Quassel rock!

Thanks a bunch jussi01, and we're looking forward to crack that bottle open for reaching the Ballmer Peak soonish :)

On an unrelated note, the Quassel team will be present at the Qt Developer Days in Munich next week, so if you happen to attend those, be sure to have a chat with us :)

Let there be, uhm, 0.3.0...1!

After quite a long while, we finally present to you a new shiny Quassel IRC release! It so happened that we decided to call it 0.3.0.1, which, as attentive readers will certainly notice in an instant, is not the long-expected 0.2.0 (and not even 0.3.0, for that matter). So, uhm, what's up with those Quassel developers and their versioning scheme?

As some of you know, we have been working on a rewrite of the old ChatWidget for quite some time now, and it was always planned that this rewrite would end up as a 0.3 release, whereas the old ChatWidget would live in 0.2. It turned out that we would not only rewrite the ChatWidget (which is now called ChatView), but also most of the client-side message handling. We have switched to a Model-View-Controller-based architecture now. Other than being much easier to maintain and improve on, this approach also allows maximum resource sharing (for example, a chatline is now only stored once, no matter how many ChatViews display it). This results in a Quassel Client that needs much less RAM than versions from the 0.2 branch. Also, we have been (and still are) working on making things more efficient both time- and space-wise, and the current 0.3.0.1 client is already much leaner and meaner than 0.2.0-rc1.

In addition to that architectural rewrite and the optimizations, with the new ChatView and its new and improved code base we could finally start adding new features and improvements to your chat window. So you'll notice a bunch of new stuff, like visible column handles, a last-seen remember line, in-buffer search and more. I won't give you a comprehensive list of new features this time, since it's just too much - just check it out for yourself!

rc1 will (hopefully) be the last Release Candidate... ever!

Just to give you a heads-up: With the release of 0.2.0 (which we expect during the next few weeks) we'll switch to a versioning scheme that is more consistent to other projects. This means that from then on, we will be releasing new patch-level releases rather than going the alpha/beta/rc cycle. The latter made sense as long as we didn't have a version that we considered complete enough to be a real release. Based on user feedback and our own experience, we feel quite confident about releasing 0.2.0 very soon now.

Releasing a candidate

After being on a bugfixing spree the past couple of weeks, the Quassel Team proudly gives you our first-ever Release Candidate of what shall become quassel-0.2.0. Since the 0.2 branch has been in feature freeze for a while, you probably won't find much new stuff (except for the occasional feature that might have crept in completely unnoticed of course ;-)), but on the other hand you will also find less bugs than in the previous releases, so grab it while it's still steaming!

Mac OS X nightlys back on track

After all the hazzle that came with the switch from svn to git and qmake to cmake, I'm glad to tell you, that the nightly builds for Mac OS X are available again. Currently there are only Mac OS X nightlys for 0.2 but that is about to change soonish. Get them as usual at http://quassel-irc.org/nightly/macosx/

Quassel at ohloh

Thanks to Flameeyes, we now have an official presence at the very cool "Social Network for Open Source Developers" called ohloh. If you are a Quassel user, don't hesitate to stop by and show the world :)

Switching to CMake

After our switch to Git as our version control system, we now also have changed our build system from qmake to CMake. Long-time Quassulans will know that we already had a CMake-based build system before switching to qmake in the first place :) Back then, we decided we'd need qmake to support Qtopia, plus CMake was quite clumsy at the time (and our old build system was uber-complex). Now, it has turned out that we can easily generate Qtopia build files from any build system, plus in the meantime our qmake stuff has grown much more complex than the old system ever was - and it came to the point where qmake just couldn't do all we needed it to do anymore.

Syndicate content