1. Mobile access and the need for bouncers/offline message handling
- “Yes, but compared to 'modern' apps IRC is very rudimentary and you would not get messages if you 'close the app'. You always have to run some secondary infrastructure like a bouncer to get offline messages or see what happened while you were away.” — dewey
- “Which is never if the person you messaged did not have a bouncer or their bouncer crashed.” — jeltz
- “You can use a bouncer on IRC to retain messages while you were offline. In reality, it's the same with every other network: you need a server which receives and retains messages while you're offline.” — WhyNotHugo
- “Mobile devices are different devices with different constraints. The main blockers are intermittent connectivity and the need to save battery life.” — cowlevel
2. IRC’s simplicity/ephemeral nature as a feature (or limitation)
- “I never worry about presence in any form of chat. I don't care if people are there when I message them; it's up to them to pick up my messages at their convenience.” — mgaunard
- “I agree. Part of the beauty is the limitations, the simplicity and transient nature of it.” — smokeyfish
- “Chatting, by design, is ephemeral and text only.” — AnonymousPlanet
- “I can only follow the conversation when I am online and there, and when I leave there is nothing to catch up to.” — pkal
3. IRCv3 extensions and modern servers/clients addressing shortcomings
- “It is the protocol's fault, and there is a solution at the protocol level: https://ircv3.net/specs/extensions/chathistory . So now, you can get messages while offline when using a modern server (eg. https://ergo.chat/) with a modern client (eg. https://codeberg.org/emersion/goguma).” — progval
- “IRCv3 gives you all of that, and I'm working on an ircd that has builtin support for multi-device access & chat history (which covers mobile between the two).” — DarkUranium
- “IRCv3 are the consensus‑based standards body for modern IRC and has ratified the WebSocket spec.” — SaberUK
- “I've set up an ergo^1 server for experimenting. Channel history is currently in draft stage; and maybe it will be forever.” — basilikum
4. Comparison with Discord/Matrix (usability, features, network effect)
- “Very bad is pretty harsh for the possibly least bad chat app that I have used. I don't like the centralization on Discord but the reason it is popular is because their app is better than the competition.” — jeltz
- “imo Telegram is the least bad chat app that I've used. Discord has a lot of UX and performance issues.” — OccamsMirror
- “Slack is a very bad that is super slow no matter what time of day I use it. It completely locks up on a spotty network. Discord works way better and their voice chat is several leagues above.” — Javier2
- “Some never left. Notoriously, some bigtech companies have an internal IRC network for tech discussions because that's one communication system that you can rely on to stay up even during catastrophic outages.” — Balinares
- “That's exactly what my tech teams did during outages of other channels. Spin up an ircd and carry on.” — smokeyfish