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

Spencer Dawkins at IETF <> Wed, 28 July 2021 17:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 06EBA3A18BA for <>; Wed, 28 Jul 2021 10:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 8ArQGHcjRj2R for <>; Wed, 28 Jul 2021 10:12:48 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::a2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 713C93A18B2 for <>; Wed, 28 Jul 2021 10:12:48 -0700 (PDT)
Received: by with SMTP id f1so635427vkk.6 for <>; Wed, 28 Jul 2021 10:12:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5NrGzOIJSLvSLOzFPlLpnM1DgaSlFd0pyQioAQj/PJQ=; b=hAQODCUJMFKzcZCY+yl2/eFdIE5OPSM+V2VCwTUkTF8u/muROYpw5oVONWpDIohbaW hrWrUP/Paz1Wrc3dKyuTwYUdVt5xKMdP07P8rs09Yuc2JRag1sMqFcop2kDnxHvPEui2 7QFBPG5KBFWhoZwOcqY0NK8V9TG5XGO4tMHzV3uvOqAULOHnpMw5W3xgfw5LveJvvD33 KsxFH/mJvS2YKlQgVMfDNE5RQbXgZqwWn+Z4tfGMwqZ1gG9CeTswTCkZneM5O5aJr+b5 1ldVKumIIEy1CPZwe13UUw5w2EcjZlNkqK5b3/VVTR1z26Mt4rqeRSi3NVRlhfRHtg/k XPWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5NrGzOIJSLvSLOzFPlLpnM1DgaSlFd0pyQioAQj/PJQ=; b=GJ31C/Ss3j8Z8bRuXRvbiQU9H1vYabG57QXUgub+7yQGNtwr1EYlthOFqckLkvceKy WM8leCXBntvPVc4nzhURXlPqm3vODH9APuZfHhDJi8s2u8qiPqMNFFsWEVSR+vHyGrMI TXAOLW34b4wzCRqJole1HDkhukNL44EXccKUQEu52Paz7TH8tviYljG5KsaTGyLU+Zi8 UjR6SwljB3tL+zcD4jzYK+9z/2T5mUKY01NINCjMI79nlVmQjB9OOsf7eRDjB0CwsbE5 KlWhSIeI7G7FOrMCklGDphKIkcg9TYCRwuzzRDI5ltmjVzEAuNtok8gX1XvgSWpfk+fF Okog==
X-Gm-Message-State: AOAM532unVhHyHouT+r4lbNaY5h+/VeVLvj+LvNZvHt0B5wcK7jpc3L2 i92D0KLwpwPQA0dD9Qmm37V//iRvQrbdkhE2QP4=
X-Google-Smtp-Source: ABdhPJz6IYcUlOSZ7ONYPO9XHiyIOUfAtkKh8n1TR1xijyumaQ8el6TGsEYXHp4tFtLrdkk1jPfr2z1htpphex9A35w=
X-Received: by 2002:ac5:c7cb:: with SMTP id e11mr1068661vkn.14.1627492366522; Wed, 28 Jul 2021 10:12:46 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Spencer Dawkins at IETF <>
Date: Wed, 28 Jul 2021 12:12:20 -0500
Message-ID: <>
To: Sean Turner <>
Content-Type: multipart/alternative; boundary="000000000000619eba05c83218de"
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 17:12:53 -0000

Hi, Sean,

On Tue, Jul 27, 2021 at 4:22 PM Sean Turner <> wrote:

> Now that it’s integrated into meetecho - the only thing you need to do is
> have somebody watch the meetecho for @mic or as MT suggested changing the
> scribes name to “Mic” and relaying anything sent to the scribe.

Thanks for the feedback. That's what I remember when I was chairing
face-to-face meetings, but wanted to push down a level or two.

What I thought, was that chairs needed to be looking at the mic queue.
which by default is toggled with the chat window, and might not have the
screen real estate to detach the chat in Meetecho, so you can move it to
another part of your screen (or another Display), or might not know you can
detach the chat window at all. If the chairs can see both (especially if
the meeting has more than one chair), ISTM that the chairs would know about
questions from jabber at the same time as everyone else.

Are there other reasons why we still need jabber scribes? (and Yoav's
suggestion to call them "jabber mediums", because they channel the words of
Those Who Are Not With Us, is brilliant).

> Personally, now that there is slack (and clones). which the rest of the
> world uses, I basically don’t use Jabber anymore.

I'm only using it at IETF meetings (and checking that it still works). And
a fair number of attendees don't know that if they're in Meetecho, the chat
IS the jabber room - I've heard "I don't have a jabber client" as recently
as Monday.

I wonder if the people I've talked to who are reluctant to install a jabber
client, or forbidden by their IT people from installing a jabber client,
would have the same problem with downloading the Slack client. I have very
little experience with the Slack web interface, but wonder if it would be
usable enough for us to point people toward it.

What I really wish, was that we'd request Meetecho to process their jabber
feed, which doesn't have the unhelpful "has joined the room"/"has left the
room" messaging that makes watching Jabber clients a pain, and store the
results someplace. This is something I miss from having Meetecho archives,
since the jabber window doesn't appear in YouTube (I just checked MOPS for
yesterday, and it's not there -

But that's a side issue, and not relevant to whether we NEED a jabber