3 ms·

Quassel IRC is another solution for this - it also works extremely well with the only downside being that it isn't tunneled over HTTP/S by default. Oh and it is

Quassel IRC is another solution for this - it also works extremely well with the only downside being that it isn't tunneled over HTTP/S by default. Oh and it is self-hosted. I can recommend it for a Windows/Linux/Android hybrid environment from personal experience

Piraty 2y ago
it supports core<--ssl-->client setup it works well indeed, i run an instance of quassel-core on a VPS for many years and connect to it through wireguard tunnel exclusively (fits nicer in my overall scheme of accessing my services)
kuschku 2y ago
While Quassel's protocol uses encryption, we've actually long considered adding support for running the Quassel protocol over websockets. With the upcoming move to Qt6 that should finally be possible without much trouble. That might solve your issues. Personally I think it's silly that the definition of "internet" has shifted so much over the past few years that "it's not HTTP" is now seen as a downside. The internet has finally become the BTX/Telex-style server/client network it was designed to replace. In fact, I'm fighting right now with my ISP (O2). They don't want to sell me a business connection. At the same time, they intentionally degrade service to prevent me from hosting services on my private connection. That includes forcefully closing PPPoE connections every 24h, assigning a random new IPv6 range every 24h (but with a valid_lft of 1.438 billion seconds), etc. But they do offer 10 consecutive phone numbers with 3x concurrent calling for private contracts.
- blkhawk 2y ago
  well I am completely with you there - but you have to remember what the words "Corporate Firewall" might mean and that the only thing apparently protecting us from a Russian takeover is closing off all outgoing ports except 80 and 443 :) I don't have an IP where i can just run Quassel on 443. Using it over websockets on a subdomain might indeed solve my troubles.

Piraty 2y ago

it supports core<--ssl-->client setup it works well indeed, i run an instance of quassel-core on a VPS for many years and connect to it through wireguard tunnel exclusively (fits nicer in my overall scheme of accessing my services)

kuschku 2y ago

While Quassel's protocol uses encryption, we've actually long considered adding support for running the Quassel protocol over websockets. With the upcoming move to Qt6 that should finally be possible without much trouble. That might solve your issues. Personally I think it's silly that the definition of "internet" has shifted so much over the past few years that "it's not HTTP" is now seen as a downside. The internet has finally become the BTX/Telex-style server/client network it was designed to replace. In fact, I'm fighting right now with my ISP (O2). They don't want to sell me a business connection. At the same time, they intentionally degrade service to prevent me from hosting services on my private connection. That includes forcefully closing PPPoE connections every 24h, assigning a random new IPv6 range every 24h (but with a valid_lft of 1.438 billion seconds), etc. But they do offer 10 consecutive phone numbers with 3x concurrent calling for private contracts.

blkhawk 2y ago
well I am completely with you there - but you have to remember what the words "Corporate Firewall" might mean and that the only thing apparently protecting us from a Russian takeover is closing off all outgoing ports except 80 and 443 :) I don't have an IP where i can just run Quassel on 443. Using it over websockets on a subdomain might indeed solve my troubles.