Quassel IRC
rimraf
Quassel IRC | rimraf | |
---|---|---|
10 | 16 | |
713 | 5,486 | |
0.6% | - | |
4.2 | 5.8 | |
5 days ago | about 1 month ago | |
C++ | TypeScript | |
GNU General Public License v3.0 or later | ISC License |
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...
rimraf
-
The Bun Shell
And npmjs.com will block your IP if you do too many downloads in on day.
Actually is says 86m a week here: https://www.npmjs.com/package/rimraf
-
PURISTA: Build with rimraf, esbuild, Turbo & git-cliff
Huge thanks to Isaacs! Rimraf comes to the rescue, providing a reliable solution for deep, recursive removal of folders and files. At PURISTA, we rely on rimraf to maintain pristine build output directories.
-
Understanding package.json II: Scripts
Avoid platform-specific commands: Avoid using platform-specific commands in your scripts. Use cross-platform tools like Node.js or Bash to ensure that your scripts work on different platforms. For instance, if you want your npm script to remove a certain directory using the rm -rf command, this would work perfectly on a Linux or Mac machine but would error out on Windows. To avoid this, you can use a cross-platform package such as [rimraf](https://www.npmjs.com/package/rimraf).
-
Extended "run all specs" feature for Cypress 10
rimraf
-
The minimal setup to package and reuse your React components
Babel will overwrite but not delete any existing files or directories in the output directory. To be sure the lib folder doesn’t contain old files you can delete it before transpiling. To do this automatically you can install rimraf and add it to the transpile script like this:
-
4 reasons to avoid using `npm link`
Many packages on npm are designed to make changes to the file-system, such as rimraf or a code linter. In an accident, the consequences of running file-system altering code can be detrimental.
-
Help Deleting STONKING File Path (over 3000 char +) WS2016 File Server
Also, rimraf seems to be popular.
-
I Prefer Makefiles over Package.json Scripts
No, that's why there's a bunch of packages such as rimraf[0] that implements that sort of functionality in a cross-platform way that most people use in their scripts
[0]: https://www.npmjs.com/package/rimraf
-
TIFU by accidentally creating over 15 million files on my computer
Something that might work: rimraf. A small node script can churn through file deletion surprisingly fast on Windows. Used to use it to clear out npm packages directories at a greater than glacial pace.
-
Said it before, I'll say it again: Software Engineers are poets.
Um actually I use rimraf
What are some alternatives?
The Lounge - 💬 Modern, responsive, cross-platform, self-hosted web IRC client
del - Delete files and directories
ZNC - Official repository for the ZNC IRC bouncer
fs-extra - Node.js: extra methods for the fs object like copy(), remove(), mkdirs()
Weechat - The extensible chat client.
mkdirp - Recursively mkdir, like `mkdir -p`, but in node.js
hexchat - GTK+ IRC client
proper-lockfile - An inter-process and inter-machine lockfile utility that works on a local or network file system.
Convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser [Moved to: https://github.com/convos-chat/convos]
cross-env
Shout - Deprecated. See fork @ https://github.com/thelounge
chokidar - Minimal and efficient cross-platform file watching library