|Subject:||Re: [PATCH] ERC: support for IRCv3.1 CAP|
|Date:||Sat, 25 Jun 2016 19:34:11 +0530|
Most popular clients and servers have already started supporting IRCv3, so I thought it would be a good idea to have some basic functionality for CAP in ERC. (Twitch already uses it to enable JOIN and PART messages, necessary for building the user list for a channel)
On Tue, Jun 21, 2016 at 3:26 AM, Vibhav Pant <address@hidden> wrote:
> The IRCv3.1 specification adds the CAP command, allowing
> client/servers to enable/disable certain capabilities. The following
> patch adds the CAP command, and the response handler for CAP LS, LIST,
> REQ, ACK, NAK and error 410 (ERR_INVALIDCAPCMD) messages.
I'm not sure that this is needed. Why does ERC need to implement CAP support?
|[Prev in Thread]||Current Thread||[Next in Thread]|