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

Bob Hinden <> Wed, 28 July 2021 18:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B82003A1B87 for <>; Wed, 28 Jul 2021 11:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id He0LwHg3JvZ9 for <>; Wed, 28 Jul 2021 11:40:46 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1F82B3A1B7F for <>; Wed, 28 Jul 2021 11:40:45 -0700 (PDT)
Received: by with SMTP id f14-20020a05600c154eb02902519e4abe10so5043225wmg.4 for <>; Wed, 28 Jul 2021 11:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=b9ykcoibHMfMu8nR241GIrWcEAFtTHOEEiUV2QRFsig=; b=KZ4ZhE6iqpwIy4n02+TRS9BId6uQmX1E9rihQdRwVXzvHquX96BDS+I5Bx0J0oAlrW fD7J5cHk22G/wFej9BC4zHBuZaweAA0LQU4ctNeWZ/98lAbC2+I7eErKxnsLmtX0iG49 Sncz5+1NU86Pi2rFrchbAKMEnksHdEEUZOWrPd+6CtfQVWh9gzfAIhOYBj74Zhw60XnQ AFRgYwcbeyJoqdghsfBoQ752yN2g+SaFrUzyRyx5WSwwB0YpdVH0h8b2hqvW+q2+KUDq W2wypfYM92yGFYFooANoH1T+aFaVoq17xMUvg/Z8ZjvngPwYgrDynPYG4oWc+Gh0zm9P 01bw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=b9ykcoibHMfMu8nR241GIrWcEAFtTHOEEiUV2QRFsig=; b=DKZ0O1uKtGAPKDKmfVr2sBNyTapk2oBVThzPVMU+88Y1JPH3LLwmCtgD8eA50C3xBp pm8h+NWZf2x3wlFAWA1iunhRhywy5xliLNdtwYlVpzF3Xw0he2yv0gUeysOn1Tpw+D9p hRv+0SX9A3yKzOIwKfVdouOatXX8Y/uZ8HZ/K/CPrT8eVmPmiyF86Vq88JUeaX9O25zO JRIfbrrlA6h8shCQyQ27I5igYM8BlMNV6bUokxZBPnwPSfBkswlrJa+8Yl2BZXsPErto FhMy/jxgtrPwtwFgKLMYK46/A3FvnlzZGDsuOlBm570URReGV1lEheUPTIm3Nzl8UcZS n5sA==
X-Gm-Message-State: AOAM531g3Swavh9WI77eqxVBlu1tvP9/jBxdMQwwDoi+qs4fu8SGVQEB TVbM6mjgloTvR519Y2ZwGzM=
X-Google-Smtp-Source: ABdhPJwTjV94h/XPmAKhV1rpmYjMkwAQvaG6TL9iW80yYSMgvSr/v/uT/4mJcAcNcoacHJibjqI/iA==
X-Received: by 2002:a05:600c:88a:: with SMTP id l10mr3612255wmp.78.1627497643126; Wed, 28 Jul 2021 11:40:43 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:659:2558:424b:e47e:dcc4? ([2601:647:5a00:659:2558:424b:e47e:dcc4]) by with ESMTPSA id s4sm857272wmh.41.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jul 2021 11:40:42 -0700 (PDT)
From: Bob Hinden <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_9F49A252-920A-467F-8194-9F57ADA5F95A"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Wed, 28 Jul 2021 11:40:39 -0700
In-Reply-To: <>
Cc: Bob Hinden <>, Spencer Dawkins at IETF <>,, Jonathan Hoyland <>, Yoav Nir <>, Sean Turner <>
To: "Andrew G. Malis" <>
References: <> <> <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <>
Subject: Re: [111attendees] So, what are jabber scribes actually doing, these days?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Jul 2021 18:40:49 -0000


> On Jul 28, 2021, at 11:37 AM, Andrew G. Malis <> wrote:
> Spencer,
> I chaired a session yesterday. I had a separate jabber session up on a second screen (using a jabber client, not Meetecho) while I was running the slides and the queue in Meetecho on my main screen. I also had a co-chair monitoring the chat while I ran everything else. Kind of clucky that you need a separate screen to see everything simultaneously, but the Meetecho interface would probably need a major redesign to fit both the queue and the chat simultaneously.

Meetecho has a feature where you can move the chat to a separate window.   It’s been there for a while.   This allows you to watch and the queue at the same time.


> Getting back to your original question, I suspect that once we're back to in-person meetings (or hybrid meetings where the chairs are local to the session), the need for an in-person jabber reporter (if not scribe) will return. With multiple chairs, a co-chair could take the role of jabber reporter. Given that everyone remote now has complete access to the in-room audio and video, I suspect that we no longer need a full-blown scribe taking notes as the meeting progresses.
> Cheers,
> Andy
> On Wed, Jul 28, 2021 at 1:19 PM Spencer Dawkins at IETF <> wrote:
> Hi, Jonathan,
> On Tue, Jul 27, 2021 at 8:08 PM Jonathan Hoyland <> wrote:
> One key thing they are doing is speaking for people for whom meetings are at 02:00am, and who don't wish to wake their families.
> Thanks! That's helpful information. I do think it's helpful to have a way to communicate into the meeting by typing.
> I did ask in my follow-up a few minutes ago whether chairs can actually watch jabber in Meetecho, given enough screen space to detach the chat, or whether they need someone who can pay closer attention.
> Best,
> Spencer
> --
> 111attendees mailing list
> --
> 111attendees mailing list