4 ms·
Disagree. As an open chat platform -- ie. not for private/confidential communications, to me, IRC is still superior to Matrix. We use it at work in parallel to
by fps_doug 5y ago
Disagree. As an open chat platform -- ie. not for private/confidential communications, to me, IRC is still superior to Matrix. We use it at work in parallel to IRC, and it still happens today (at least with elements.io) that a message or two can get lost when you restart your client in an unfortunate moment, and sometimes channel user lists get out of sync, so you're addressing a person that's not there, or suddenly someone replies you don't see in the user list. It's happening rarely, but it does, and it is annoying.
IRC's concept of requiring an active TCP connection for your session is archaic but dead simple, and the only times you have to wonder whether or not someone received your message is if they got a ping timeout shortly after, and the user list might get out of sync once in a honeymoon when there's a net-split. Nothing about IRC changes anymore, so you won't get surprised by regressions and bug fixes every month. I can see how people miss long multi-line messages and animated gifs in IRC, but I just don't. It's straight forward text communications, no bullshit.
- fastball 5y agoI genuinely don't understand how you are concerned about "losing messages" when that is literally the baseline for IRC. Every person needs their own bouncer if they don't want any message to be lost to them when their machine disconnects from the internet. And if your bouncer loses connection you won't get the messages either.
- iforgotpassword 5y agoIRC doesn't lose messages. Everyone you see in the channel gets the message, everybody else doesn't. No guessing games. That's what gp meant.
- _flux 5y agoShould be the same for Matrix really, if your client manages to send it to the server.
- kitkat_new 5y ago> and it still happens today (at least with elements.io) that a message or two can get lost when you restart your client in an unfortunate moment Is that unlucky moment during Element sending/trying to send the message to the server? In this case Element stores messages now until they are sent (since 1.7.26). Otherwise, don't see how this could happen.