21–30 of 446 posts
At work, it has only ever been Slack. Some older employees recall using Skype for Business.
One thing I miss about IRC is the lack of a typing indicator.
It applies heavy pressure and behind that is the motive to monetise attention. Snapchat is the worst for this; it notifies your recipient once you start typing.
At its core, I agree that the bare-bones nature of IRC can be wonderful. But all of the modern services like Teams, Slack and Discord, have seamlessness between client devices as their first priority. People leave their laptop, go to the bathroom, get their phone out and go on typing. I used IRC for a brief period even after we began to have multiple devices. It was always through some kind of proxy, or basically an…
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, because somehow those messengers couldn't successfully move to phones, we had the same problem again in the mobile world: 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 work with flaky connections on mobile. It obviously requires 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].
> The reliability and lack of bloat that are inherent to IRC ultimately also means that there are a number of fancy modern features that Discord has that IRC lacks, a big one being the inability to view backlogs of conversations that transpired while one was not connected to an IRC server. Although IRC does not itself provide this functionality, the extremely simple nature of IRC allows for a couple of lightweight op…
> The reliability and lack of bloat that are inherent to IRC ultimately also means that there are a number of fancy modern features that Discord has that IRC lacks, a big one being the inability to view backlogs of conversations that transpired while one was not connected to an IRC server. Although IRC does not itself provide this functionality, the extremely simple nature of IRC allows for a couple of lightweight op…
> The reliability and lack of bloat that are inherent to IRC ultimately also means that there are a number of fancy modern features that Discord has that IRC lacks, a big one being the inability to view backlogs of conversations that transpired while one was not connected to an IRC server. Although IRC does not itself provide this functionality, the extremely simple nature of IRC allows for a couple of lightweight op…
there's built in support for this https://www.unrealircd.org/docs/Channel_history
Absolutely fantastic that it was finally added but IRC is 34 years old, and this has been an essential feature of chat services for at least 20 of those years.
I'd love to see it's introduction now save IRC but given the seeming resistance to adding it, one wonders how long any other improvements will take.
> The reliability and lack of bloat that are inherent to IRC ultimately also means that there are a number of fancy modern features that Discord has that IRC lacks, a big one being the inability to view backlogs of conversations that transpired while one was not connected to an IRC server. Although IRC does not itself provide this functionality, the extremely simple nature of IRC allows for a couple of lightweight op…
Discord's search function is so bad it's essentially unusable so having the backlog is often useless, however the ability to "pin" a useful message or discussion by getting a link is very relevant.
Baseline IRC doesn't have message addressing, regardless of backlogging.
You need the "message-tags" extension (https://ircv3.net/specs/extensions/message-tags) and message-ids support (https://ircv3.net/specs/extensions/message-ids.html) for that to even be entertained, plus probably echo-message (https://ircv3.net/specs/extensions/echo-message). I've no idea how well those are supported in servers, to say nothing of clients (which would need a way to surface message ids, and possibly permalinks).
At that point, you probably also want the WIP chathistory extension (https://ircv3.net/specs/extensions/chathistory) which provides backlog support.
> The reliability and lack of bloat that are inherent to IRC ultimately also means that there are a number of fancy modern features that Discord has that IRC lacks, a big one being the inability to view backlogs of conversations that transpired while one was not connected to an IRC server. Although IRC does not itself provide this functionality, the extremely simple nature of IRC allows for a couple of lightweight op…
I like that IRC has no backlog support. When you join a channel it's like you actually joined a room. You don't know what they were talking about when you weren't there.
One thing I miss about IRC is the lack of a typing indicator.