Convos VS WeeChat

Excellent idea! You'll have a mature, open standard protocol under the hood, with no vendor lock-in, excellent extensibility, and great modern frontends like The Lounge (https://thelounge.chat/) or Convos (https://convos.chat/) to choose from (and you can choose). - Source: Hacker News / 4 months ago

For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine. Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on... - Source: Hacker News / about 1 year ago

FWIW TheLounge [1] and Convos [2] can front-end an IRC server giving it much of the look of a modern client and also chat persistence when using TheLounge in private mode. The trade-off in my opinion is scalability. With a bog standard IRCD I can handle tens of thousands of clients per node. Adding web persistent chat adds memory usage. [1] - https://github.com/thelounge https://thelounge.chat/ [2] -... - Source: Hacker News / over 1 year ago

IRC is a mature, extensible, open protocol, with a wide variety of server and client implementations to suit many use cases, servers can be self-hosted and federated, and modern web-based clients like The Lounge or Convos offer a user experience equivalent to Discord, Slack, etc. Source: over 1 year ago

And there are some great web-based clients like the Lounge and Convos that offer an equivalent UX to Discord or Slack, are open-source, self-hostable, and based on a mature, reliable, and extensible open protocol. Source: about 2 years ago

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] - Source: Hacker News / 4 months ago

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... - Source: Hacker News / 9 months ago

With this particular linked page, it's just the change log. The actual website is at https://weechat.org/. - Source: Hacker News / 11 months ago

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/. - Source: Hacker News / 11 months ago

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. Source: about 1 year ago