QuasselBy Kunal Mehta
I've recently switched from using ZNC+Textual over to Quassel. It has the same idea as a bouncer, with a "core" that runs on your server, and a "client" that you run locally. I've been using ZNC for over 2 years now, so this was a pretty big switch for me. I did it for a few reasons:
- Textual didn't really handle crappy networks well, constantly disconnecting
- Textual 5 was a paid upgrade, something I wan't too enthusastic about after already paying for it
- Textual was having issues loading past scrollback, requiring force quits and manual cache clearing
- ZNC would fall over and die when freenode netsplit.
In addition, I'm getting a second laptop soon and want to be able to use both for IRC and keep everything in sync. Quassel seems to make that feasible, as the core manages scrollback rather than individual clients being responsible.
Overall, I'm pretty happy with Quassel so far. It handles terrible network connections pretty well, and makes it extremely convenient to go back days in scrollback. The UI on the other hand leaves a lot to be desired for...Textual's was far superior. My main issue so far has been that until a message you typed has been sent, it doesn't show up in the scrollback. There are also some issues with the channel selector picking the wrong channel.
I'm slightly concerned about how much space quassel will use for logs. It's already using 33MB after only a week of usage, and I tend to be in some highly active channels.
For now I've left ZNC running as a backup, but I'll shut it down in another week. I still have an irssi session running in a screen on a server I'm logged into with mosh, which is handy for being on both sides of freenode netsplits :P