3 ms·
Quassel isn't a traditional bouncer though. It doesn't proxy the IRC protocol but uses a custom one between core and client, so you can properly run multiple cl
by iforgotpassword 6y ago
Quassel isn't a traditional bouncer though. It doesn't proxy the IRC protocol but uses a custom one between core and client, so you can properly run multiple clients connected to one core, and it will synchronize the read/unread state, highlights etc. between clients.
I prefer it over the lounge because it's not web based. I'm old and hate everything web based.
- gramakri 6y agoAh, good to know. Is that a requirement that the client and the core talk IRC to qualify as a bouncer? I guess that will also rule lounge as a bouncer since afaik it talks HTTP and not IRC. ZNC is a proper bouncer then.
- tenebrisalietum 6y agoWell back in the day your connection to a university shell account might have been through dialup, so using the low-bandwidth IRC protocol to talk to the BNC was perfect.
- iforgotpassword 6y agoI don't think there is a formal definition, but for the longest time that's how it has been, so people might assume they can just use any IRC client to connect to the bouncer, so it might be worth pointing that out for clarification when talking about the lounge or quassel.
- heavyset_go 6y agoThere's also a Quassel web front end here[1]. I prefer the way Quassel handles IRC, so I use the daemon and various front ends, including the web one. [1] https://github.com/magne4000/quassel-webserver https://github.com/magne4000/quassel-webserver