2016-05-07 00:59:34 +00:00
|
|
|
|
|
|
|
|
PRE-RELEASE
|
|
|
|
|
===========
|
|
|
|
|
|
2016-05-07 05:07:16 +00:00
|
|
|
- hexchat: missing nick list
|
2016-05-07 05:52:33 +00:00
|
|
|
--- works if we reply NAMES to WHO queries, but that throws andchat
|
2016-05-07 07:02:17 +00:00
|
|
|
--- support WHOX just for hexchat??
|
2016-05-07 00:59:34 +00:00
|
|
|
|
2016-05-07 06:38:25 +00:00
|
|
|
- yaaic/atomic: doesn't recognise the room join (even with autojoin disabled)
|
2016-05-07 05:07:16 +00:00
|
|
|
|
2016-05-07 06:58:19 +00:00
|
|
|
- andchat: WHO list doesn't get /cleared/ on room quit+autojoin
|
|
|
|
|
|
2016-05-07 05:07:16 +00:00
|
|
|
- part all nicks upon upstream server disconnection
|
2016-05-07 00:59:34 +00:00
|
|
|
|
2016-05-07 01:55:29 +00:00
|
|
|
- test the current password auth
|
|
|
|
|
|
2016-05-07 07:02:17 +00:00
|
|
|
- detect our own /me messages + don't echo back
|
|
|
|
|
|
2016-05-07 00:59:34 +00:00
|
|
|
|
2016-05-07 05:07:16 +00:00
|
|
|
|
|
|
|
|
|
2016-05-07 00:59:34 +00:00
|
|
|
WISHLIST
|
|
|
|
|
========
|
|
|
|
|
|
2016-05-07 05:07:16 +00:00
|
|
|
- send client keepalives (PING) /and/ ensure we get a reply (PONG)
|
|
|
|
|
|
2016-05-07 00:59:34 +00:00
|
|
|
- client version sync (CTCP VERSION)
|
|
|
|
|
|
|
|
|
|
- client descriptions (CTCP USERINFO)
|
|
|
|
|
|
|
|
|
|
- support changing nick (via reconnecting)
|
|
|
|
|
|
|
|
|
|
- expose upstream op status
|
|
|
|
|
|
2016-05-07 01:55:29 +00:00
|
|
|
- support WHO
|
|
|
|
|
|
|
|
|
|
- support WHOIS
|
|
|
|
|
|
|
|
|
|
- support USERIP/KILL/KICK for ops
|
2016-05-07 00:59:34 +00:00
|
|
|
|
|
|
|
|
- use CTCP chat to support irc-special characters in chat messages (colon, newline)
|
|
|
|
|
|
2016-05-07 01:55:29 +00:00
|
|
|
- respond to CAP LS 302 (hexchat) in some way that'll kick us into a modern protocol mode
|
|
|
|
|
|
|
|
|
|
- support SASL PLAIN authentication as well as just classic PASS
|
|
|
|
|
|
|
|
|
|
- threadsafe access to libnmdc hub options
|
2016-05-07 00:59:34 +00:00
|
|
|
|
2016-05-07 05:07:16 +00:00
|
|
|
- do we need to send the same payload in our PONG response?
|
|
|
|
|
|
2016-05-07 00:59:34 +00:00
|
|
|
|
|
|
|
|
|
2016-05-07 02:46:23 +00:00
|
|
|
|
2016-05-07 00:59:34 +00:00
|
|
|
REF
|
|
|
|
|
===
|
|
|
|
|
|
2016-05-07 07:02:17 +00:00
|
|
|
https://www.alien.net.au/irc/irc2numerics.html
|
|
|
|
|
|
2016-05-07 00:59:34 +00:00
|
|
|
http://www.anta.net/misc/telnet-troubleshooting/irc.shtml
|
|
|
|
|
|
|
|
|
|
https://tools.ietf.org/html/rfc2812
|
|
|
|
|
|
|
|
|
|
http://www.irchelp.org/irchelp/rfc/ctcpspec.html
|
|
|
|
|
|
|
|
|
|
https://en.wikipedia.org/wiki/List_of_Internet_Relay_Chat_commands
|
|
|
|
|
|
|
|
|
|
https://en.wikipedia.org/wiki/Client-to-client_protocol
|
|
|
|
|
|
|
|
|
|
https://wiki.mibbit.com/index.php/Ctcp_(version)
|
|
|
|
|
|
