diff options
author | Vincent Ambo <tazjin@google.com> | 2020-02-24T16·35+0000 |
---|---|---|
committer | Vincent Ambo <tazjin@google.com> | 2020-02-24T16·35+0000 |
commit | 190378ad0512a218fe52b3dad1911b561f5a1506 (patch) | |
tree | 6adefd00d2b228d08b6b0bea53f643ddaf16bbbf /docs/CODE_OF_CONDUCT.md | |
parent | 6380c168c954f725ea68f4b2181c47dea33a35d8 (diff) |
feat(3p/emacs/rcirc): Implement support for IRCv3 server-time r/578
This adds very basic capability[0] and message tag[1] support to rcirc which is used to implement support for the IRCv3 server-time[2] spec. During connection setup, the server is asked to list its capabilities and the `server-time` capability is then blindly requested from it (the CAP handler code does not check whether server-time is actually part of the listed capabilities). rcirc does not need to know whether this negotiation succeeded, because server time tags will either be sent or not. By default rcirc prints all timestamps at current-time. A new variable `rcirc-last-message-time` has been added which, if set, overrides this timestamp. It is set by the message handler after parsing IRCv3 tags. Thanks to William Cummings for nudging me in the direction of his post about adding ZNC playback support to rcirc[4], from which some parts of this code were taken. This has been tested with IRCCloud's bouncers. [0]: https://ircv3.net/specs/core/capability-negotiation [1]: https://ircv3.net/specs/extensions/message-tags [2]: https://ircv3.net/specs/extensions/server-time-3.2.html
Diffstat (limited to 'docs/CODE_OF_CONDUCT.md')
0 files changed, 0 insertions, 0 deletions