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

Carsten Bormann <cabo@tzi.org> Thu, 29 July 2021 23:07 UTC

Return-Path: <cabo@tzi.org>
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 766A93A0DCE for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 16:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0xvHzgcXqXEx for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 16:06:56 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B7073A0DD6 for <111attendees@ietf.org>; Thu, 29 Jul 2021 16:06:56 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GbR4G1JpQz31PV; Fri, 30 Jul 2021 01:06:54 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20210729202945.8BE96254E6F2@ary.qy>
Date: Fri, 30 Jul 2021 01:06:53 +0200
Cc: 111attendees@ietf.org
X-Mao-Original-Outgoing-Id: 649292813.636721-2026796c24405763fd30eab5c2c352d1
Content-Transfer-Encoding: quoted-printable
Message-Id: <509FBB5E-19B8-43A9-A824-3AB0FD7664A1@tzi.org>
References: <20210729202945.8BE96254E6F2@ary.qy>
To: John Levine <ietf@johnlevine.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/jvyPsDnDitID2L_9jeelXU7Aykg>
Subject: Re: [111attendees] So, what are jabber scribes actually doing, these days?
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 23:07:01 -0000

On 2021-07-29, at 22:29, John Levine <ietf@johnlevine.com> wrote:
> 
> According to Carsten Bormann  <cabo@tzi.org>:
>> -=-=-=-=-=-
>> On 29. Jul 2021, at 21:43, Jay Daley <jay@ietf.org> wrote:
>>> 
>>> Umm … have you tried having the two windows side by side?
>> 
>> Yes, but then I can’t read the CodiMD window.
>> 
>> Increasing the number of windows that I have to juggle is not a winning strategy for focusing my attention on the content of the meeting.
> 
> Trying to arrange a set of panes that differ for each user (some look
> at codimd, some at local copies of slides, some at documents for
> reference, some at the people who are talking, ...) and fit them into
> a fixed layout is a losing battle.

Er, that was not what I was asking for.

I was asking that the information that meetecho manages is designed in such a way that it can stay it its window.  I have no idea why you think the other items need to be addressed by meetecho.  (I don’t even know why the superfluous function to replace the slides by a codimd iframe is in there, who wants to use that?)

Clearly, the participant names are unnecessarily large.  This causes a spacing where even the microphone line doesn’t fit on the screen and requires scrolling; I no longer can see who is speaking (as this is inexplicably below the microphone line).  So I need to run meetecho at 67 % scaling.  This means that the constant-width multi-purpose column is now wide enough that it would also be no problem to optionally fit the chat inside it.  These are all design options that need to be considered rationally.

> Perhaps you could invest in a bigger screen.  They're pretty cheap these days.

The screens are cheap.  The time I need to use to juggle all those windows is not.

Grüße, Carsten