Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Twitch handling #798
As Twitch gains popularity, it would be good for eggdrop to keep up with that. Right now, there are IRC gateways that connect to twitch servers, which Eggdrop can (somewhat) handle connecting to. However, many features are enabled via CAP, which bastardize the irc protocol by prefixing things like
This is IRCv3 stuff which isn't really limited to Twitch. I imagine once Eggdrop handles IRCv3 tags in general, the Twitch specific information can easily be handled by user scripts.
I think Eggdrop should be able to look past these tags if present to keep existing binds functioning without requiring any user configuration. Then a new bind similar to RAW, but with IRCv3 information as an extra parameter in the proc, would be useful for custom processing. Could be a string as-is, or an array from the semi-kolon separated data.
Twitch is in my opinion too far from IRC standard to warrant special attention, but generic IRCv3 handling is indeed something worth paying attention to.
CAP tags is indeed what adds this extra stuff while membership is required to receive join/parts from server.