3 ms·
If someone interest in recent development of IRC protocol, you might be interest in the IRCv3 Working Group[1] where they're working toward improving the curren
by sirn 12y ago
If someone interest in recent development of IRC protocol, you might be interest in the IRCv3 Working Group[1] where they're working toward improving the current IRC protocol (and already being used in number of networks and clients).
[1]: http://ircv3.atheme.org/ http://ircv3.atheme.org/
- aw3c2 12y agoDoes it require encrypted connections?
- sirn 12y agoYou mean the IRCv3? I believe encrypted connection is still optional.
- voltagex_ 12y agoYou may be able to help influence it at https://github.com/ircv3/ircv3-specifications/issues https://github.com/ircv3/ircv3-specifications/issues
- Zev 12y agoIt does not require encrypted connections, although it does have extensions to indicate that future connections should occur over TLS (through the optional `tls` extension in IRCv3.1) and there is discussion for standardizing IRC over SCTP in IRCv3.3
- qznc 12y agoYou might want SILC, but it is pretty much dead.
- qznc 12y agoOne big issue with IRC is the missing support of Unicode. An IRC log is a potential mixture of latin1, utf8, and whatever encoding user write. I fear that cannot be fixed in a backwards-compatible way.
- sirn 12y agoThat's a big one indeed. I'm currently running a small private IRC server (~50 users) for local community speaking Thai; the best solution I found for encoding issue is to force everyone to use Unicode. However, this is a really hard thing to do, as most do not see benefit over whatever they're using (tis620 in my case) or benefit over upgrading their dated client.