[111attendees] Re: So, what are jabber scribes actually doing, these days?

Bron Gondwana <brong@fastmailteam.com> Thu, 29 July 2021 22:58 UTC

Return-Path: <brong@fastmailteam.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E984E3A0D40 for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 15:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=fastmailteam.com header.b=MZQ+NeBc; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=meBnkHiF
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 oueeDqAT40vi for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 15:58:57 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A9043A0D35 for <111attendees@ietf.org>; Thu, 29 Jul 2021 15:58:56 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 42F9A3200915 for <111attendees@ietf.org>; Thu, 29 Jul 2021 18:58:55 -0400 (EDT)
Received: from imap43 ([10.202.2.93]) by compute6.internal (MEProxy); Thu, 29 Jul 2021 18:58:55 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm3; bh=SUHI/gt HRRLATZAu9443Lh9pvM9iO3I2IUJCgOPO3Ns=; b=MZQ+NeBcM9iUR0AuHTO7Ttu lg/j0fU191wpx4dy5qCVaUqrxBZvhgQThsYOWiWOAPyDXha8srnsjgRUvibndVgc PDsmNeGNhCjgehYrcF+h/SxOaq9Oc0XGdEe4Z4EYxlb4WGds/G/GeF6p95u4ZH+R SdEPl/KmEuybTigyqbuWKbMYjwOfTAZqcmIO6pOcbYxS2vo/JUNEihF2pIz8xBvs JbLXgdPL6PkJhP6sBcespCKsBzjLPbMujKkPpqSd2OVN6SbzSBAs6AbPxeueDBFV 0JW5uOVZwxSm3CYxIfknQizx3kJV9iSs/70uB8xUCSYV+O55QmDR/WuZieKVN+Q= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=SUHI/g tHRRLATZAu9443Lh9pvM9iO3I2IUJCgOPO3Ns=; b=meBnkHiFljfUkyJd+4tA76 Hg4IH7rqBq/oNFTbeNLmxduPADjVh5F36JfNYldYfKmnjhL/JUw6e3VOBlhKXfLt 3O369OoGatMAHBskeFNvorAIqK6JFiO9Qfy7HHXRSDhDN2DDMTpYU9S+JcPGLkwe PZ4JSF9Y1HN2Jted86nQip0MCILChY1Nv065bgdo3yX/cI7yKXO/8nLpRHKWCYpB AYCz6pWl6xVk7bZCtia89jEay8k4/nRUvQfql9LFuoOcCJ2Cf9Q95aFAX/kBtN1L t3qt8O5gvcb+95Nv6C4pwK34I/W04pNSEhNcW/9FFkIXsO+f0yQsGP19S8yE16cA ==
X-ME-Sender: <xms:rjIDYfR33iYWH2_nZ5KejApjoqTsFaIqgAOE2TkWLmfBNhZq-BKjkw> <xme:rjIDYQxnZOF8JXUZ3V2lNxLhK5f0bl7gE8-vGtgVfEHzOEQS-eJOwbQZVfbMbIplP SIVIhVnEvM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrheefgdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpedtheetgeefve etudffveetheffgfehhfdvveekuefhheeuteduhefggeeikeejteenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrhhonhhgsehfrghsthhmrg hilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:rjIDYU0AxYriP5QEWY2gZkiXxY0nqWLxtq2YjehbUxiFCJy0zDcZwg> <xmx:rjIDYfC6BWaytzv0Bb1oyUhuaVbdpR6HI3zKhsXcyMIfPCcHRtu5CA> <xmx:rjIDYYj850fVRt1OBgQSIkBKTAxUduhj-GXeTGu3MPbzpNRqYLQWAA> <xmx:rjIDYTttwp2XgIHLeUjWPBQSbmJAO_mG17ASkwqsb9l1aUP8yBntag>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 52384AC0E77; Thu, 29 Jul 2021 18:58:54 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1002-g563fbe43fc-fm-ubox-20210727.001-g563fbe43
Mime-Version: 1.0
Message-Id: <5d8b7c55-55a3-4732-812c-a230ee81948f@dogfood.fastmail.com>
In-Reply-To: <7898431E-8B87-44CE-A68D-DC093908495F@ietf.org>
References: <CAKKJt-ex+bzDO5t4Uznd2aPHf8xP8ZX-JZx5VUSd-7hADsWTGQ@mail.gmail.com> <CAKKJt-c6CyQxpfW+2wVg+NbomwtBPUXZGjL-W8iuQfmaunQmcw@mail.gmail.com> <20210727204916.GA15189@faui48e.informatik.uni-erlangen.de> <30AFBC23-155E-4BE1-A33C-908FD17BC73C@sn3rd.com> <CAKKJt-d5vbdDNc3BFKLJu7t51Jf30GLQi3-YV3pfZODCOFBO9g@mail.gmail.com> <5A346DF0A2B69EB397207C72@PSB> <7898431E-8B87-44CE-A68D-DC093908495F@ietf.org>
Date: Fri, 30 Jul 2021 08:58:34 +1000
From: "Bron Gondwana" <brong@fastmailteam.com>
To: 111attendees@ietf.org
Content-Type: multipart/alternative; boundary=439ff63cb7644fb68cabda08fa86f470
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/ipJvCDyhH6Mu7Uak69pbqhWMXas>
Subject: [111attendees] =?utf-8?b?PT9VVEYtOD9RP1JlOl9fU28sIF93aGF0X2Fy?= =?utf-8?q?e=5Fjabber=5Fscribes=5Factually=5Fdoing=2C_=3F=3D__these_days?= =?utf-8?q?=3F?=
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 22:59:01 -0000

On Fri, Jul 30, 2021, at 05:21, Jay Daley wrote:
> No we have absolutely not pushed Meetecho into being "just a contractor", they are a valued partner and we work very well together.  If you have any doubts about that then ask them directly.  
> 
> It is disappointing that you have escalated a personal concern that you have with our services into such a strong criticism when that is entirely unsupported by any evidence.  

Jay, I agree with your sentiment here - this attitude to Meetecho is counterproductive.  They've done great work for the last couple of IETFs and the experience is improving each time.  I have particularly appreciated the embedded slide management, and I'm sure that will be even better next time too.

Regarding the specific interface issues that remain, I do think there's a question of "where do we propose improvements in a way that will be noticed"?  I've seen the suggestion made very many times that the "speaker" area (where the video shows) should have additional lines for each person sending anything, rather than that information being at the top of the participant list.  This is much more like the experience with other chat systems, for example Zoom shows either a photo or a blank item for somebody who isn't currently sending video, but they're otherwise treated "the same" as a person sending video in terms of real-estate and where to look for their presence by default.

Right now with meetecho, my eyes are normally at the video are when people are speaking, but if a non-video person is speaking I need to look across to the other side of the screen to see the audio indication.

And as was also suggested in this thread, you can't scroll the participant list to find someone to chat to, because they jump to the top when they are sending, then back to alphabetical position.  This is also a usability pain.  Separating "the list of participants" (which wouldn't move about) and "the list of people sending something" with the video and audio indications being together in one place would be a significant improvement.  And as an additional benefit, when you're looking at the chat window, you would still be able to see all the details of who is sending (including yourself - if you're sending then the indicator of your own audio should be the same as the indicator of everyone else's audio, rather than being in yet a third location up under your own name).

So those two names would appear in the right hand side, and also still have their name in the participant list, and the video feeds would each have a "here's what's being sent".  Chairs would always have a presence on the right, with whatever they were currently sending - and the "participants" tab would only have the list of participants, and not be a place you needed to go to see activity, so you could mostly keep the chat tab open.

Bron.


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com