Quassel IRC
Converse.js
Quassel IRC | Converse.js | |
---|---|---|
10 | 17 | |
713 | 3,013 | |
0.6% | 0.2% | |
4.2 | 9.2 | |
5 days ago | 2 days ago | |
C++ | JavaScript | |
GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Quassel IRC
-
IRC Is the Only Viable Chat Protocol
> 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/
- mIRC i början av 2000?
-
Looking for C++ projects to contribute to
Quassel IRC: A modern, cross-platform, distributed IRC client. Tech Stack: C++, Qt.
-
Client that simultaneously supports both PC and Android?
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
-
Is/are there any FOSS Discord Client for Android?
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.
-
Saturday APPreciation (Feb 05 2022) - Your weekly app recommendation/request thread!
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 .
-
Thoughts on the state of the freenode IRC network - Edward Kmett
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...
-
AWESOME WINDOWS TOOLS
Quassel - Quassel IRC is a modern, cross-platform, distributed IRC client.
-
Convos solves IRC's persistence problem
Seems really similar to Quassel (https://github.com/quassel/quassel/), though I don't believe that has a webclient...
Converse.js
- ConverseJS 10.1.7 with an important XEP-0474 support fix used in ejabberd – XMPP
-
How to build an AI chatbot with Openfire and OpenAI Chat Completion
ConverseJS is a popular Javascript XMPP client that implements a full range of XMPP extensions. Also available as a plugin for openfire — inverse-openfire-plugin and can be installed on openfire with a few clicks.
- Converse.js 10.1.2
-
An actually private messaging self hosted server
I agree. IMHO the best variant is then to use something that is truely free. Like XMPP. There are a lot of servers and many clients to chose from and I can strongly recommend converse.js as a web client. It supports different ways of end to end encryption but I would recommend OMEMO which is basically the same encryption idea that you find in Signal.
-
Xmpp Bot with its own address.
Hello, I recently started exploring xmpp, with snikket app and conversejs.org
-
Matrix was worth the effort to self host.
It is Converse.js (https://conversejs.org/) packaged into a one-click install for openfire (from the web admin). So, one-click install for an xmpp web client.
-
Ask HN: What is your recommended stack for real time chat?
My choice, because it's the stack I know very well, would be Prosody ( https://prosody.im/ - I'm one of the devs) and a web client such as Converse.js ( https://conversejs.org/ ). XMPP is highly extensible, Prosody is highly modular, which make them a good foundation for building on top of.
That said, the right stack is generally the one that matches your requirements, and (if this isn't primarily a learning exercise) whatever you're most familiar with. The hardest part of building a Discord or Slack-like in 2022 is actually not the technical stuff. There are many comprehensive open-source products already out there that compete with these companies, such as Mattermost, RocketChat and Element.
-
No white list registering with conversejs.org
Tried to register with conversejs.org today and got an error "your IP is not whitelisted".
- Best open source protocol to fork?
-
NEEE HELP!
Maybe you are remembering this bug from some months ago? It appeared exactly as if this was (accidentally) uploading keys to the user's XMPP server (not Converse.js's server) and publishing them.
What are some alternatives?
The Lounge - 💬 Modern, responsive, cross-platform, self-hosted web IRC client
JSXC - :speech_balloon: Real-time xmpp chat application with video calls, file transfer and encrypted communication.
ZNC - Official repository for the ZNC IRC bouncer
Movim - Movim - Decentralized social platform
Weechat - The extensible chat client.
Candy - JavaScript-based multi-user chat client for XMPP.
hexchat - GTK+ IRC client
Kaiwa - [UNMAINTAINED] A modern XMPP Web client
Convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser [Moved to: https://github.com/convos-chat/convos]
Kontalk - Kontalk official Android client
Shout - Deprecated. See fork @ https://github.com/thelounge
CHVote - Electronic vote system, version 1.