Weechat VS Quassel IRC

WeeChat[0] with Bitlbee[1] supports a metric assload of services, albeit by pretending they're IRC (which does work - I spent years in weechat/irssi with bitlbee talking to various people on disparate services.)

Or if you're just after Telegram/WhatsApp, nchat[2] is ok (I can vouch for the Telegram half only.)

[0] https://weechat.org

[1] https://wiki.bitlbee.org

[2] https://github.com/d99kris/nchat

And UnrealIRCD still rocks. For a quick-and-dirty setup I've deploy ng-ircd but Unreal has always been my go-to for anything serious. If nothing else it can be useful as a backup or internal platform during the rare events that Slack or Discord are having an incident. The common complaint is a lack of channel back-log but it can be front-ended with TheLounge [1] or Convos [2]. I personally prefer to handle that with gnu screen or tmux and WeeChat [3].

[1] - https://github.com/thelounge

[2] - https://github.com/convos-chat/convos/

[3] - https://weechat.org/

The link posted was to the dev blog, the actual website can be found at [0]. On the blog, the right side menu under "Links" also links to the website.

[0] - https://weechat.org/

I’m afraid you’re in the wrong subreddit. This subreddit is dedicated to WeeChat the IRC client., not the proprietary messaging app built by Tencent.

First off, grab yourself an IRC client. On their connection info page Hackint has information for both WeeChat and Hexchat, but you could use any IRC client.

That's nothing to do with weechat? https://weechat.org/

Gajim is for XMPP. For IRC you need Hexchat or Weechat or something like that.

I am not familiar with HexChat but you might consider using a different IRC client that allows you to silence anything/everything by default and only alert you on specific keywords you are interested in. If you like command line tools, consider trying out WeeChat IRC client [1] It is very customizable and there are many scripts for it.

[1] - https://weechat.org/

> But all of the modern services like Teams, Slack and Discord, have seamlessness between client devices as their first priority.

Can't speak for the others, but Teams is really hit-or-miss. Missed notifications, missed messages, out of order messages. Then it appears to be fixed for three months only to happen again. It mostly seems to happen on Android.

In general, you're right, multi-device appeared to have been solved for IM - at least MSN messenger and Skype had it - right around the time when the smart phone came around, but then we had the same problem again in the mobile world, because somehow those messengers couldn't successfully move to phones: WhatsApp and the likes was bound to one device again. They added web access later, but that was more of a hack than true multi-device support.

The big problem the phone messaging apps solved was that their protocols didn't require a persistent connection. Theoretically, all the other protocols, MSN, ICQ, Skype, IRC could have been extended to support this too, but it's always faster to just build something new and be first to market.

If you want to use IRC today and have that modern multi-device experience, IMO the most decent solution is Quassel[1] (and Quasseldroid for Android). It's like a bouncer, but uses a custom protocol between the bouncer (quassel-core) and the GUI (quassel-client), so that it can perfectly sync state across all devices, and with flaky connections on mobile. It obviously required you to run the core on some server so it's accessible from everywhere, so nothing for "normies" as TFA calls them, but to me it's what makes IRC usable in the modern world. I wouldn't want to use irssi in a screen via ssh in termux on my phone.

The next best thing, if you're a Web 2.0 aficionado is probably The Lounge[2].

[1] https://quassel-irc.org/

[2] https://thelounge.chat/

Quassel IRC: A modern, cross-platform, distributed IRC client. Tech Stack: C++, Qt.

You can use a bouncer to do this. ZNC is the most popular. Quasse is a different take on the bouncer, where you have a special client that logs into your Quassel server, and the server logs into IRC. Has certain advantages, like more seamless scrollback and so forth. A variant take on this is irccloud, which is probably the "best" if you just want something turnkey that works with minimal fuss. It has good push notifications, a good web client, and excellent mobile clients

I use purple-discord (libpurple/Pidgin plugin) + BItlBee (IRC chat gateway, libpurple variant) + Quassel (distribued IRC client, like a bouncer) on a home server, and use Quasseldroid to connect on mobile. I would eventually like to simplify this setup.

Personally, I use a self-hosted "Core" (server) of Quassel I compiled from source and host remotely. Attach to the Core "locally" on a ZeroTier LAN network through a persistent physically independent WireGuard/reverse proxy/edge node microserver using various open source apps (preferably compiled from source). On Android I use QuasselDroid and of course compiled from source .

I've been a massive user of IRC since the mid 90s... have written lots of bots, scripts etc plus set up plenty of stuff to deal with being able to disconnect your client without missing out on anything (currently use https://quassel-irc.org/ with the daemon on a VPS). I was even l33t enough to "read bitchx.doc" back in the day...

Quassel - Quassel IRC is a modern, cross-platform, distributed IRC client.

Seems really similar to Quassel (https://github.com/quassel/quassel/), though I don't believe that has a webclient...