![]() ![]() Documentation of what Twitch does with IRC can be found at Most importantly Twitch only losely follows the IRC spec, so arguing that a client doesn't properly follow a spec when you have issues with Twitch is a really slippery slope. Note that you'll have a pretty bad IRC experience in Thunderbird with Twitch due to a multitude of reasons, including that you can't send the CAP requests to get JOIN/PART/MODEs, that you won't see any of the special messages like responses to commands or USERNOTICES and many, many more little annoyances. ![]() I've attached my config keys for the (working) Twitch IRC account I have configured. Based on my further explanations following this I think it'd be better to treat Twitch as a separate provider. We could add non-standard code to try and detect twitch, however that'd have to happen based on the server URI, and since there are about three aliases that strikes me as rather complicated. ![]() TMI (Twitch's IRC network) works just fine in Thunderbird when the password is properly set as server password and not as account password (so with the pref Patrick described). Verification and it may not be changed once registered. It is possible to send multiple PASS commandsīefore registering but only the last one sent is used for ![]() Must match the one contained in the C/N lines (for servers) or I Send a PASS command before any SERVER command. Currently this requires that clients send a PASSĬommand before sending the NICK/USER combination and servers *must* Password can and must be set before any attempt to register theĬonnection is made. The PASS command is used to set a 'connection password'. The correct implementation would allow connecting without any issues.Īttachment: RFC 1459 Chapter 4.1 (only relevant section) The currently wrong implementation causes the response "Improperly formatted auth" and disconnects the Client. Password: 'oauth-token in the format "oauth:asdasd234asd234ad234asds23xyz" (without quotes)' One of these examples is the IRC Server. Thunderbird starts with USER or NICK, which causes issues with Servers strictly sticking to the RFC. The IRC connection initialization is in the wrong order.Īccording to the RFC 1459 (Chapter 4.1, see attachement), the PASS message HAS TO BE the FIRST message sent. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |