Re: System generated chat messages during WG sessions

Toerless Eckert <tte@cs.fau.de> Thu, 05 September 2024 20:47 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995E3C16942D; Thu, 5 Sep 2024 13:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.66
X-Spam-Level:
X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qA5IjRbK0fMh; Thu, 5 Sep 2024 13:47:26 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1065C169404; Thu, 5 Sep 2024 13:47:18 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4X0BHg5nrFznkpt; Thu, 5 Sep 2024 22:47:11 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4X0BHg4grJzkxCp; Thu, 5 Sep 2024 22:47:11 +0200 (CEST)
Date: Thu, 05 Sep 2024 22:47:11 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: System generated chat messages during WG sessions
Message-ID: <ZtoYz78OBV5F0T7Z@faui48e.informatik.uni-erlangen.de>
References: <900A9A09-B013-47EA-856B-5706EBCE088F@ietf.org> <ZtnxQSJcv9-LqhHo@faui48e.informatik.uni-erlangen.de> <CAA=duU1qG5O3r13P0eB8qMSpyNQKACZXKLc1tyJwNfrg-E16yQ@mail.gmail.com> <Ztn_2d64MuB-SgOo@faui48e.informatik.uni-erlangen.de> <CAA=duU31C8Kr=SNL1GOAmpicmm_PFnAX=Nuo+UMqLeDLY+FYpg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAA=duU31C8Kr=SNL1GOAmpicmm_PFnAX=Nuo+UMqLeDLY+FYpg@mail.gmail.com>
Message-ID-Hash: OK23BGTAKM6HV45OHUNQQKR6ZNZNPCY6
X-Message-ID-Hash: OK23BGTAKM6HV45OHUNQQKR6ZNZNPCY6
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: wgchairs <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/JLy6jCpoH0xe45KOW0BCSOLP5cc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

On Thu, Sep 05, 2024 at 03:05:01PM -0400, Andrew G. Malis wrote:
> Toerless,
> 
> If the autogenerated messages are in the chat and you don't like them, it's
> really easy to run the chat through a text filter to get rid of them.

My point was that the auto-generated messages belong into the transcription track of the
youtube video. That's where you'd search for them and click on them to get to a particular part of
the recording.

The chat is already messsy enough as it stands. Unless we really need to have information in it
as we did in the past for audio-only participants, i don't think we shouldhave this additional
metadata in it.

Cheers
    Toerless

> Cheers,
> Andy
> 
> 
> On Thu, Sep 5, 2024 at 3:00 PM Toerless Eckert <tte@cs.fau.de> wrote:
> 
> > On Thu, Sep 05, 2024 at 02:28:59PM -0400, Andrew G. Malis wrote:
> > > Toerless,
> > >
> > > There are people that like to read the chat, or incorporate the chat into
> > > the minutes, without having to watch the entire video.
> >
> > That's fine. Nothing i proposed argues against it. I just don't want the
> > chat to be cluttered
> > with information about the actual primary meeting track - especially
> > because i do not want
> > to kill off asynchronous chat discuss that's explicitly NOT in-sync with
> > th primary WG
> > track.
> >
> > Cheers
> >     Toerless
> >
> > > Cheers,
> > > Andy
> > >
> > >
> > > On Thu, Sep 5, 2024 at 1:58 PM Toerless Eckert <tte@cs.fau.de> wrote:
> > >
> > > > My 22cents:
> > > >
> > > > I would not like for the chat to be scattered by this metadata because
> > we
> > > > should already
> > > > have an actual metadata stream in the videos: the CC (close caption
> > > > track). AFAIK, all
> > > > IETF recordings on youtube have it. Seemingly some are done
> > manual/better,
> > > > most are
> > > > automatic (suck rocks - especially with non native speakers).
> > > >
> > > > Anyhow: What the IETF tooling team seemingly does not do right is to
> > > > enable the youtube
> > > > transcription feature from this CC track. When i go to most other
> > > > (non-IETF) videos
> > > > with CC, then i can click on "Show Transcript" at the bottom of the
> > > > youtube description.
> > > > This will then pop up the transcript - and then you can scroll/search
> > and
> > > > jump to specific
> > > > transcript points.
> > > >
> > > > Seems obvious to me, that we would want any section markers like
> > > > slides/presentations/speakers
> > > > on the microphone to be in this transcription track.
> > > >
> > > > Of course: If youtube allows multiple tracks, then it would be fine to
> > > > also include the
> > > > chat as a secondary caption track. But let's not consider it to be a
> > > > primary track
> > > > for the session recording.
> > > >
> > > > Cheers
> > > >     Toerless
> > > >
> > > > On Thu, Sep 05, 2024 at 12:42:37PM +0100, Jay Daley wrote:
> > > > > Starting a new thread on this.
> > > > >
> > > > > Meetecho have confirmed that having the system generate chat
> > messages is
> > > > pretty straightforward so I want to ask what action points are the most
> > > > useful for such a message, assuming we don’t want too many such
> > messages as
> > > > that will clutter the chat.
> > > > >
> > > > > So far we have:
> > > > >
> > > > > - When a new presentation is started so that it contextualises the
> > chat
> > > > messages after that.
> > > > >
> > > > > The only other one I can see might be useful is:
> > > > >
> > > > > - When a poll is initiated and/or closed, perhaps with the result
> > copied
> > > > to the chat.
> > > > >
> > > > > Yes/no? and any others?
> > > > >
> > > > > Jay
> > > > >
> > > > > --
> > > > > Jay Daley
> > > > > IETF Executive Director
> > > > > exec-director@ietf.org
> > > >
> > > > --
> > > > ---
> > > > tte@cs.fau.de
> > > >
> >
> > --
> > ---
> > tte@cs.fau.de
> >

-- 
---
tte@cs.fau.de