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

John C Klensin <> Thu, 29 July 2021 14:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3D4293A243A for <>; Thu, 29 Jul 2021 07:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id I3go_4iK7FwK for <>; Thu, 29 Jul 2021 07:18:03 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BCF803A2438 for <>; Thu, 29 Jul 2021 07:18:03 -0700 (PDT)
Received: from [] (helo=PSB) by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1m96rJ-000GKd-VE; Thu, 29 Jul 2021 10:18:01 -0400
Date: Thu, 29 Jul 2021 10:17:56 -0400
From: John C Klensin <>
To: Carsten Bormann <>
cc:, Spencer Dawkins at IETF <>, Sean Turner <>
Message-ID: <998CB12942BA60232E560663@PSB>
In-Reply-To: <>
References: <> < om> <> <> <> <5A346DF0A2B69EB397207C72@PSB> <>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
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: Thu, 29 Jul 2021 14:18:09 -0000

--On Thursday, July 29, 2021 15:23 +0200 Carsten Bormann
<> wrote:

> On 2021-07-29, at 15:09, John C Klensin <>
> wrote:
>> impossible (or, at least non-obvious) to have both the
>> chat and participant frames open at the same time.  
> It's much worse: You can't have the important part of the
> participant frame (who is speaking) open at the same time you
> scroll for a potential attendee. Fortunately, there is the
> jabber entry/exit trace…

Sorry... saw and responded to Spencer's comments before reading
this.  And, yes.

> The important part of the participant frame (who is speaking,
> are the chairs present, what is the queue — IN THAT ORDER)
> needs to be visible at all time.  But I'd rather have that,
> the participant list, and the chat visible all three,
> somewhere on the vast amounts of blank space that meetecho
> leaves on my window.

Yes to that too.   I'm still (or again) using a separate Jabber
login to give me more control over that situation (and to take
advantage of having a lot of screen real estate, the ability to
at least somewhat control character sizes with that other
client, etc.  And, because people speak without turning on
video, burying the "who is speaking" information partway down
the participant frame rather than occupying a separate line in
the blank space to which you prefer seems, well, sub-optimal.  I
agree about the other parts of your "important" list too, but
"who is speaking" is the really critical bit.