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

"John R. Levine" <johnl@iecc.com> Fri, 30 July 2021 00:02 UTC

Return-Path: <johnl@iecc.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 25A223A10E5 for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 17:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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=iecc.com
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 8cWFXEnw6S1P for <111attendees@ietfa.amsl.com>; Thu, 29 Jul 2021 17:01:57 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 679A63A10DB for <111attendees@ietf.org>; Thu, 29 Jul 2021 17:01:57 -0700 (PDT)
Received: (qmail 74354 invoked from network); 30 Jul 2021 00:01:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=1226f.61034173.k2107; bh=nJSFD5P6BJINyc/8DKWQHhE93mm2vrKseyg5Z/GUmhg=; b=pNt4zZqO3UD0nQ52DmrXUOnVnCNSt6jGXM2GoIV/EFoCdTsRc5iYrBLoKFrO7wUNO0q6s/UAqlkrqviPOxxuQSWusdtJTLAv70TDm2TCp5C5Px0B8T8ISK+T3//9CvOEdeSbaKYae53l6hpu3HpDXVxUi/e0VMfUqEClD+itDzUCfhAPXgf5aZdJhcvJfB7PthjrSRJ2yuFxtwpMF5i4hrMvpxHb9kJYo1NFGHz4bcc1AuzGPK3BfBKcp17hFfsa9NDpWhtD8AAagKolja80XP/kBPO3vD6mzmjK2d5rYir/dCAwwjurSjpPQnn1gELfZbj6GVTLVWCjdNDuyYGX0g==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Jul 2021 00:01:54 -0000
Received: by ary.qy (Postfix, from userid 501) id 3FD68255069C; Thu, 29 Jul 2021 20:01:52 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id D52E7255067E; Thu, 29 Jul 2021 20:01:52 -0400 (EDT)
Date: Thu, 29 Jul 2021 20:01:52 -0400
Message-ID: <8642d57b-46f9-2938-4997-df15b97cb5@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: 111attendees@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <509FBB5E-19B8-43A9-A824-3AB0FD7664A1@tzi.org>
References: <20210729202945.8BE96254E6F2@ary.qy> <509FBB5E-19B8-43A9-A824-3AB0FD7664A1@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-904353286-1627603312=:22066"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/CPk_jPtpDCdTlhZOt6hgH9fdvuU>
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: Fri, 30 Jul 2021 00:02:04 -0000

> 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.

I suppose we could ask Meetecho to offer a more compact style. I would 
prefer not to make the names much smaller since I find them hard enough to 
read as it is, but if they can do it by twiddling style sheets, or even 
better letting users twiddle their own style sheets, sure.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly