[00:40] -lugito:#lubuntu-devel- [T54: Properly implement different wallpapers for different monitors] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T54#2717
 The version of quassel we ship by default is messed up.
 Can't connect to quassel-core
 Can only directly connect to irc network. There's no option of connecting to a core.
 We get a welcome dialogue box which takes details and connects to irc networks only.
 But I actually ran it from a persistent usb. The usb is a bit slow. That dialogue box opened a bit late than quassel opened. Now, before opening of that dialogue box, there was an option to connect to a quassel-core. It disappeared the moment the welcome screen appeared.
 Someone verify.
 If we are shipping an irc client, I suggest hexchat. Quassel which cannot connect to a core is just useless. The user will have to install quassel-client separately. Seems redundant.
 @kc2bez uses quassel. Can confirm imo.
 Just Installed hexchat to compare usage. Hexchat is clearly lighter than quassel.
 Connected yo same network, same user same channel #lubuntu
 Minimised.
 Hexchat 9MB
 Quassel 23MB
 Telling from qps.
 @tsimonq2 wxl: what say?
 hexchat is not Qt driven
 Quassel is last i checked
 and that's heavier.
 🤷🏻‍♂️
 Even tho hexchat isn't qt driven. It's lighter. Also, the quassel core issue I pointed.
 And don't know why, in the quassel we ship, the default network, named "Lubuntu IRC" tries to connect to ubuntu servers buy on port 8001.
 It should be 6697/6667 na?
[02:07] <guiverc> I've tested the default many times (ISO QA-testing) & connected fine to #lubuntu; usually pm myself on this box; so it works (I have no idea about port)
 Didn't connect on 8001 on my system coz sophos I assume but default is 6667 only right?
 Idea: to make it super lite, we give an executable which points to kiwirc in browser. It's not fully capable as compared to a client but does the job and uses already installed good ol Firefox. What say?
 It's bit of a strech but hey! Less resources used.
[13:21] <kc2bez> The_LoudSpeaker: I use quassel. I uninstall the monolithic application and install quassel-client. I have a separate Ubuntu server that just runs quassel-core. Here is the quassel wiki page to get you started: https://bugs.quassel-irc.org/projects/quassel-irc/wiki
 @kc2bez [<kc2bez> The_LoudSpeaker: I use quassel. I uninstall the monolithic application …], I also use quassel only. Can't connect to my quassel core using the default client that we ship. Wanted you to confirm if you can.
[17:21] <kc2bez> No, you can't connect to a core with the client we ship, quassel client is  a separate package. 
 @kc2bez [<kc2bez> No, you can't connect to a core with the client we ship, quassel client …], We should ship the combined core-client that quassel provides or not ship it at all imo.
 Honestly hexchat is better than what we ship currently and it's light also.
[17:47] <kc2bez> The client we ship works without the core, it is all together as one. 
 Hexchat is lighter.
[17:49] <kc2bez> ok
 @kc2bez [<kc2bez> The client we ship works without the core, it is all together as one.], Even if its all together one, it's tweaked to not connect to other core. We should remove that tweak atleast.
[18:13] <kc2bez> It isn't tweaked, they are 2 separate applications for 2 different purposes. It is all explained on the quassel wiki page. 
[18:14] <kc2bez> As far as an alternative IRC client that is lighter it would be best if it was a qt application.
 @kc2bez [<kc2bez> It isn't tweaked, they are 2 separate applications for 2 different purp …], I see. I will have to take a look.
 @kc2bez [<kc2bez> As far as an alternative IRC client that is lighter it would be best if …], H
 @kc2bez [<kc2bez> As far as an alternative IRC client that is lighter it would be best if …], Hexchat can be ported?
 https://github.com/kvirc/KVIrc