From 6a7847f71bcb2689ccc0bb8febdb54b35fb6d480 Mon Sep 17 00:00:00 2001 From: "." <.@.> Date: Tue, 10 May 2016 19:16:39 +1200 Subject: [PATCH] preparations for 1.1.0 release --HG-- branch : nmdc-ircfrontend --- _dist/README.txt | 25 ++++++++++++++++++------- typedefs.go | 2 +- 2 files changed, 19 insertions(+), 8 deletions(-) diff --git a/_dist/README.txt b/_dist/README.txt index ae78c14..dd651f2 100644 --- a/_dist/README.txt +++ b/_dist/README.txt @@ -18,6 +18,7 @@ Tags: nmdc, AGPLv3 - NMDC server's title exposed as IRC channel topic - Login with passworded nick (classic `PASS`, not `SASL`) - Full nick list integration including op status +- Support IRC client changing nick via NMDC upstream reconnection - Automatic join to single-enforced chatroom - Multithreaded - Single binary deployment @@ -29,6 +30,8 @@ Tags: nmdc, AGPLv3 Automatically join clients to the channel (default true) -bind string The address:port to bind to and listen for clients on (default ":6667") + -hubsecurity string + Nick used for administrative events (default "Hub-Security") -servername string Server name displayed to clients (default "nmdc-ircfrontend") -upstream string @@ -40,25 +43,33 @@ Tags: nmdc, AGPLv3 NMDC's smaller community has standardised around comparatively few protocol implementations by means of necessity. In comparison, there are a lot of IRC client implementations with slightly differing interpretations of the protocol. -[b]Everything works:[/b] +Everything works: - Hexchat - Mango IRC - AndroIRC - Lite IRC - Mutter - Weechat +- mIRC 7 +- HoloIRC (after version 4.1.0) -[b]Usable, with bugs:[/b] -- HoloIRC - Can't parse client tag, upstream bug https://github.com/tilal6991/HoloIRC/issues/140 +Usable, with bugs: +- HoloIRC (4.1.0 and earlier) - Can't parse client tag, upstream bug https://github.com/tilal6991/HoloIRC/issues/140 - AndChat - Duplicate usernames appear, upstream bug https://github.com/znc/znc/issues/424 - Irssi - Ignorable warning "critical nicklist_set_host: assertion 'host != NULL' failed" -- mIRC 7 - Doesn't understand PRIVMSG with blank sender, causing upstream system messages to instead appear in the Server window -[b]Unusable:[/b] -- Yaaic - doesn't properly understand/parse the room join -- Atomic - doesn't properly understand/parse the room join, crashes on `PRIVMSG` with blank sender +Unusable: +- Yaaic and Atomic - doesn't properly understand/parse the room join =CHANGELOG= +2016-05-10 1.1.0 +- Feature: Support renaming own client during connection (`/nick`) +- Enhancement: Option to set Hub-Security nick (needed for initial CTCP, upgraded after upstream connection) +- Compatibility: Apply user-agent-specific hacks for mIRC and Atomic clients not nicely handling PRIVMSG with blank sender +- Compatibility: Better heuristic detection for client tag extraction +- Fix an issue causing the default client tag (nmdc-ircfrontend) to briefly appear in the NMDC user list, by (briefly) delaying the upstream join unless CTCP VERSION response comes in +- Fix an issue generating malformed version numbers in NMDC client tag + 2016-05-08 1.0.0 - Initial public release diff --git a/typedefs.go b/typedefs.go index e097f9d..ad12382 100644 --- a/typedefs.go +++ b/typedefs.go @@ -19,7 +19,7 @@ along with this program. If not, see . */ const ( - APP_VERSION = "1.0.0" + APP_VERSION = "1.1.0" APP_NAME = "nmdc-ircfrontend" BLESSED_CHANNEL = "#chat" // must be lowercase BLESSED_CHANNEL_MODE = "n" // means that you have to be in the channel to chat, but that's it