Trial chat services: matrix and zulip

Robert Sparks <> Thu, 01 October 2020 14:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03D603A109F for <>; Thu, 1 Oct 2020 07:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JZticKH9mY0t for <>; Thu, 1 Oct 2020 07:25:23 -0700 (PDT)
Received: from ( [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 549B63A1099 for <>; Thu, 1 Oct 2020 07:25:23 -0700 (PDT)
Received: from unescapeable.local ([]) (authenticated bits=0) by (8.16.1/8.16.1) with ESMTPSA id 091EPKWm024951 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <>; Thu, 1 Oct 2020 09:25:21 -0500 (CDT) (envelope-from
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default; t=1601562321; bh=4P77fZgLBdUi4kQPhqpVc/yxzJAuOXdFnT81Ci8hhpM=; h=From:To:Reply-To:Subject:Date; b=gv6/lxlDCOXHbBWyq2ZbPpjzpYv3QiolZXDuWbaP8QKKn89hsI3HxCFegx7IM/uLS 8ChTTYv01bzO/7O6OF6giGFzSt4sXzZbajP1dmUJ+/rT+uW/2+gJFbLfUzoibQfQAy V+qf29E0j4REfJJWKIR+leRiqEFuZCBn2US51IEA=
X-Authentication-Warning: Host [] claimed to be unescapeable.local
From: Robert Sparks <>
Reply-To: "" <>
Subject: Trial chat services: matrix and zulip
Message-ID: <>
Date: Thu, 1 Oct 2020 09:25:20 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <>
X-Mailman-Approved-At: Thu, 01 Oct 2020 07:32:32 -0700
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 01 Oct 2020 14:25:25 -0000

We are deploying trials of the matrix and zulip chat services to gain
operational experience and get community feedback about how well these
services meet the need for IETF related chat.

We have clear evidence from the IETF 107 post-meeting survey
( that many
IETF participants find jabber a significant problem.  This is partly due to
difficulties in finding a free jabber service and partly due to client 
There are two paths to try to resolve these problems, one is to improve the
IETF jabber service and the other is to switch to an alternative groupchat
solution.  The community has already taken a step on the latter path 
with the
introduction of an IETF Slack space, and we want to ensure that this path is
properly explored by widening the range of options to well established
free/open source tools.

The installs currently have almost no local configuration or customization.
Over the next few weeks, we will be exploring reconfiguring them to use
datatracker credentials for sign-in, and explore bridging between these
systems, Slack, and Jabber. One consequence of these explorations is 
that there
will  likely be times, outside of meetings, when accounts will be 
disrupted or
even removed and will have to be recreated. Initially, we suggest you use an
email address for the username on each service.

We considered running these trials using instances run by the Zulip or 
communities. We went with instances operated by the secretariat to learn 
would be needed if the community felt self-hosting chat was important in the

The services can be found at and

Any matrix client can be used with the trial matrix server. There is also
a web client available at at

Similarly any zulip client can be used with the trial zulip server, which
has a built in web interface.

We would like feedback on how well each client meets chat needs during
meetings, both the full online IETF 109 meeting, iterims, adhocs, and 

Around December, we will assess our experiences and the feedback received to
inform what chat services we provide in the future and how we will operate
them. In January, these trial instances will be taken down. We do not 
intend to
preserve or migrate any account configuration or chat history from the trial
instances as we move forward.

This does add to the potentially confusing large number of places 
might take place. We hope to address that with some level of bridging, 
at least
with Jabber, but have been cautioned by the respective development 
that bridging between Zulip and Matrix is unsatisfying since the 
models in the two applications are so different.

The chat services are intended to be explorational and informal. However,
please treat them as contexts where contribution rules apply (See

We are not, at this time, planning to host jabber accounts. We may 
revisit that
as an option as we continue to gather more feedback.

Please send feedback on the services to