4 ms·

> The reliability and lack of bloat that are inherent to IRC [...] First off, I love IRC and always will. But boy, the author sure must have a stable internet

by kyrofa 3y ago

> The reliability and lack of bloat that are inherent to IRC [...] First off, I love IRC and always will. But boy, the author sure must have a stable internet connection. In my experience one blip means a lost message with no indication that it's been lost. That is not my definition of reliable.

progval 3y ago
IRC uses persistent TCP connections as a transport. You can't lose a message in the middle of a stream without the whole connection being closed, and your client would tell you about that.
- kyrofa 3y ago
  > You can't lose a message in the middle of a stream without the whole connection being closed, and your client would tell you about that. I don't know what to tell you other than "that doesn't mesh up with the reality of my experience" shrug. Even if they did tell me about a connection issue (which they often didn't), those messages are still gone with no indication that I missed anything ("hey your connection blipped" != "here are the messages you missed while you were gone").
  - kaoD 3y ago
    Well, I don't know what to tell you other than "that doesn't mesh up with the reality of TCP".
  - progval 3y ago
    What client do you use? I can try looking for why it would hide it from you.
kakwa_ 3y ago
This was not a really issue... as long as you had access to a shell on a reliable server to screen+irssi (or tmux+weechat if you felt fancy).
- kyrofa 3y ago
  Well sure, I used a bouncer like everyone else because of this issue (and for persistent presence since I dealt with people in different timezones), but that is a workaround for a protocol that isn't actually reliable, which is sort of my point.
  - kakwa_ 3y ago
    Yes, I know :) My comment was ironic, solution like that are not practicable for common users. The rise of alternative chat platforms (discord, matrix, slack) really demonstrates IRC was too limited. I will remember it foundly but the era where IRC was the dominent open channel chat platform is at its end. I just hope Discord will not be it's long term replacement.

by kyrofa 3y ago

progval 3y ago

IRC uses persistent TCP connections as a transport. You can't lose a message in the middle of a stream without the whole connection being closed, and your client would tell you about that.

kyrofa 3y ago
> You can't lose a message in the middle of a stream without the whole connection being closed, and your client would tell you about that. I don't know what to tell you other than "that doesn't mesh up with the reality of my experience" shrug. Even if they did tell me about a connection issue (which they often didn't), those messages are still gone with no indication that I missed anything ("hey your connection blipped" != "here are the messages you missed while you were gone").
- kaoD 3y ago
  Well, I don't know what to tell you other than "that doesn't mesh up with the reality of TCP".
- progval 3y ago
  What client do you use? I can try looking for why it would hide it from you.

kakwa_ 3y ago

This was not a really issue... as long as you had access to a shell on a reliable server to screen+irssi (or tmux+weechat if you felt fancy).

kyrofa 3y ago
Well sure, I used a bouncer like everyone else because of this issue (and for persistent presence since I dealt with people in different timezones), but that is a workaround for a protocol that isn't actually reliable, which is sort of my point.
- kakwa_ 3y ago
  Yes, I know :) My comment was ironic, solution like that are not practicable for common users. The rise of alternative chat platforms (discord, matrix, slack) really demonstrates IRC was too limited. I will remember it foundly but the era where IRC was the dominent open channel chat platform is at its end. I just hope Discord will not be it's long term replacement.