| > There's also the fact that most IRC clients suck, with interfaces that look and control like xterm circa 1980. Fine for the people that read Hacker News, offputting for everyone else. This is konversation in 2017: https://blogs.kde.org/2017/09/05/konversation-2x-2018-new-us... The version of Quasseldroid I am working on right now: http://i.imgur.com/obsJDyg.png Textual, a macOS IRC client: https://www.codeux.com/textual/public/images/v600media/Yosem... > A reference implementation of a WIP RFC is rather different from a thing you can download and install and have working right now in a server that isn't likely to change their implementation in a way that makes those features unusable (since they're headline features being sold to enterprises). That’s why the IRCv3 Working Group isn’t some people in an ivory tower, but actually the implementers – the developers of the largest IRCd implementations, and of all major clients cooperate to design and ship new functionality. This means that basically every client and server has an implementation by the time it ships. > SASL is nice, but unless you're into something like Okta or some other homegrown thing, most are going to use plain old LDAP/AD The guys at CoreOS have a simple single-click deployed system for bridging LDAP/AD for that purpose. Alternatively, RedHat also has a solution for that, and provides enterprise support for their product (Keycloak), too. |
