Re: [Tools-discuss] matrix tests

Matthew Wild <mwild1@gmail.com> Sun, 13 December 2020 23:01 UTC

Return-Path: <mwild1@gmail.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8EF3A0114 for <tools-discuss@ietfa.amsl.com>; Sun, 13 Dec 2020 15:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oqQgb8roU_OP for <tools-discuss@ietfa.amsl.com>; Sun, 13 Dec 2020 15:01:39 -0800 (PST)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A985A3A0100 for <tools-discuss@ietf.org>; Sun, 13 Dec 2020 15:01:39 -0800 (PST)
Received: by mail-qv1-xf35.google.com with SMTP id l7so7050000qvt.4 for <tools-discuss@ietf.org>; Sun, 13 Dec 2020 15:01:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eZQJA3rJbipN0h0658vRMAFBPAp3ZlUBOk0WAuGZ218=; b=LwefgI6MrGMHrDYFcYPnQIwu/krpgubNKJfVKfOYtySLzg86HcorcwGcNMWQKoanxB aI/H8koB7wRKOtqC7hseSpdNqpEDWlKuUuvX4Rb1mIT8QcsZhB4UNgh70gAfLTqvWXck Myndpvpp6b05+lwJXA3i9EBp4axrtNRdXcyd1xtDZOrh3rmASNK9z5gTzPLHUbkiLYtJ Z/8UzQ4hGTTyiNsqxvZpx17dcWMSeKOmTGtgU4xuTdGXRguFjMZ6pOyovf+U8VylxLUb QGnJ+Sq2W5ApEYHrvoNZxrmFSA+7pV0SyOGL0W4YWbo+jc+lSQ9BiYCnnwr9UnjydIAM MX7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eZQJA3rJbipN0h0658vRMAFBPAp3ZlUBOk0WAuGZ218=; b=diRMVFgma4eK+bDiOeettGIY9kmu9NmuTcbUUTU1ixprTx6WdHV+aVbpnO4fszlM/w bST5yMCo+HWZmvb2W5AY8c7xDiTWdUcgxe4FJP4/mJmfjB93rSJzBAYvegKO1lPDpKUs TiF64tBRjZqM3nnuswr1A70dfe5d1zM2PezlzmoyUPvKNOps6tJmyZtWOBBhyiZb36NA YTfLX7JdWBM5NKSzcLnXKyX9MVdq1XsDRQF0VzYkll5Samu5b9ifW5D8Eyk27zCOFqoF GfQ/qqYSr+Ca5X2gUHeUWSM1lJxu64G72wNuHenOAzE2IOPyRrX5TBvP2pOTFQkOlrd8 zXNA==
X-Gm-Message-State: AOAM533qmDEzz4MCdyWwjYSYuLGSSIJtLBF83bONOb93fBUuJmc/Qs6o HRw68BJ8VWelscTfeA0nrvlBtX39pQmQveoZD0L24S7G+IA=
X-Google-Smtp-Source: ABdhPJxnapw9/iPSePnkTj6PLDjaewzTl081MOVOyUnC176SsF4PtnUm2o6e3/vEjNzq4NXwrejZQ9IacfSdg1Q8NeE=
X-Received: by 2002:ad4:45a9:: with SMTP id y9mr29842763qvu.15.1607900498589; Sun, 13 Dec 2020 15:01:38 -0800 (PST)
MIME-Version: 1.0
References: <e547d7be-8838-ce7f-fad5-61af474f7d12@cs.tcd.ie>
In-Reply-To: <e547d7be-8838-ce7f-fad5-61af474f7d12@cs.tcd.ie>
From: Matthew Wild <mwild1@gmail.com>
Date: Sun, 13 Dec 2020 23:01:26 +0000
Message-ID: <CAJt9-x7pQSMhOodtpG8Cjnjncj7EsjNUeWQKVfTDfUNo8VjzQg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Tools Team Discussion <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000d7de705b66082d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/HFL-AURfTdPQ1CmFs5oqfj5cHoc>
Subject: Re: [Tools-discuss] matrix tests
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Dec 2020 23:01:41 -0000

Hi Stephen,

On Fri, 11 Dec 2020 at 20:52, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

> I've run my own matrix server for the last few years for
> non-IETF purposes.
>
> I appreciate the ability to use matrix as mobile clients
> for matrix are more widely available and more up to date
> than for jabber. That (better clients) might be more
> noticeably beneficial when we get back to f2f meetings,
> as in WFM-mode, I have plenty of screen real-estate.
>

I'm curious which clients you tried. On Android there's (at least)
Conversations and yaxim, iOS has (at least) Siskin and Monal. All are
actively developed with releases in the past months, and all of them (to
answer a point you made later in your email) support editing messages.

I had expected there to be a matrix room corresponding
> to each jabber room but I didn't investigate much due
> to the TZ issues and the fact that jabber was fine.
>

There is a Matrix bridge that should allow anyone to join the XMPP chats
from any Matrix client, as I understand it.

I think the main feature in matrix clients that I like
> that beats jabber is the ability to edit messages after
> they've been sent. I'm not sure how that'd pan out with
> the jabber logs, but am happy to do a test if that's
> useful. I'm also happy to connect and play about in
> general if that's helpful, just ping me.
>

As mentioned above, all modern clients support editing messages.

This is a common pattern. Clients such as Pidgin and Adium are popular
among people who are used to Jabber/XMPP from years ago, but both those
projects are seriously lacking behind today's standards. Unfortunately I
think many people form opinions of XMPP based on their experiences with
older "previous generation" software, but modern XMPP has long moved on. I
know the Pidgin folks are keen to catch up, but they have other
project-wide priorities they are focusing on.

On the logs note, I believe with the current setup editing a message will
probably display the updated message as a new message. As with a number of
things in the current IETF XMPP deployment, this is something that could be
improved upon. If the decision is made to stick with XMPP then I think a
bit of modernization of the deployment would be a great thing, and
something I'd be happy to help with.

Regards,
Matthew