4 ms·

Because: * No clients support multimedia - animated GIFs, videos, audio, images, video/audio calls - only Quassel has web previews and that's about it * E2E e

Because: * No clients support multimedia - animated GIFs, videos, audio, images, video/audio calls - only Quassel has web previews and that's about it * E2E encryption doesn't exist properly * Signing up to protect usernames is a pain in the ass, especially if people span networks and assuming networks even have something like NickServ * Users are require to have a bouncer to have some chat persistence * No clients offer convenience features such as search * It's a pain in the ass to manage channels to just chat * Clients can't handle mobile connections well I'm sure I've forgotten other problems the protocol has.

chipotle_coyote 8y ago
I'm not sure any of those are issues that couldn't have been addressed by now through a new version of the protocol, though; what I'm trying to get it is that it's sort of weird to me that IRC in 2019 isn't materially different than IRC in 1994. IRCv3 addresses a whole lot of those problems, for instance, and there's nothing that technically could have prevented it from addressing them 10 years ago.
- dcbadacd 8y ago
  IRCv3 brings a bunch of really nice features I'm so happy to have, but it's really the clients that need a lot of work in addition to just IRCv3 features. Image, video and audio inlining is still something that no client does and the standard can't help with and that's a huge con for most users. What the standard could help with is standardizing markdown formatting, some method of E2E encryption, better SASL (with registration, key rollover/update and distribution between your clients).
Marsymars 8y ago
> * No clients support multimedia - animated GIFs, videos, audio, images, video/audio calls - only Quassel has web previews and that's about it Textual supports a bunch of inline media: https://help.codeux.com/textual/release-notes/Release-Notes%3A-Version-7.0.7.kb https://help.codeux.com/textual/release-notes/Release-Notes%...
- dcbadacd 8y ago
  Unfortunately Textual is MacOS only?
  - Marsymars 8y ago
    Yes, that is the case, and is unfortunate for the IRC ecosystem, but it's not the case that "no clients support multimedia".
    - dcbadacd 8y ago
      Given OSX's marketshare it's only a rounding error away from being "no clients support multimedia" unfortunately.

chipotle_coyote 8y ago

I'm not sure any of those are issues that couldn't have been addressed by now through a new version of the protocol, though; what I'm trying to get it is that it's sort of weird to me that IRC in 2019 isn't materially different than IRC in 1994. IRCv3 addresses a whole lot of those problems, for instance, and there's nothing that technically could have prevented it from addressing them 10 years ago.

dcbadacd 8y ago
IRCv3 brings a bunch of really nice features I'm so happy to have, but it's really the clients that need a lot of work in addition to just IRCv3 features. Image, video and audio inlining is still something that no client does and the standard can't help with and that's a huge con for most users. What the standard could help with is standardizing markdown formatting, some method of E2E encryption, better SASL (with registration, key rollover/update and distribution between your clients).

Marsymars 8y ago

> * No clients support multimedia - animated GIFs, videos, audio, images, video/audio calls - only Quassel has web previews and that's about it Textual supports a bunch of inline media: https://help.codeux.com/textual/release-notes/Release-Notes%3A-Version-7.0.7.kb https://help.codeux.com/textual/release-notes/Release-Notes%...

dcbadacd 8y ago
Unfortunately Textual is MacOS only?
- Marsymars 8y ago
  Yes, that is the case, and is unfortunate for the IRC ecosystem, but it's not the case that "no clients support multimedia".
  - dcbadacd 8y ago
    Given OSX's marketshare it's only a rounding error away from being "no clients support multimedia" unfortunately.