Re: System generated chat messages during WG sessions
Aaron Parecki <aaron@parecki.com> Thu, 05 September 2024 20:51 UTC
Return-Path: <aaron@parecki.com>
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 E0B82C1388B9 for <wgchairs@ietfa.amsl.com>; Thu, 5 Sep 2024 13:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=parecki.com
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 5JzsqqxiRJm2 for <wgchairs@ietfa.amsl.com>; Thu, 5 Sep 2024 13:51:37 -0700 (PDT)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB338C14F5F7 for <wgchairs@ietf.org>; Thu, 5 Sep 2024 13:51:37 -0700 (PDT)
Received: by mail-vk1-xa32.google.com with SMTP id 71dfb90a1353d-5012813249cso97231e0c.2 for <wgchairs@ietf.org>; Thu, 05 Sep 2024 13:51:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki.com; s=google; t=1725569496; x=1726174296; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FGoMR4Rh2+I0F+KnAtAj4qDB1TwB5zXtDQwb8przRbI=; b=ZHNnIgwUuFBWy0ePdigflqQkqs7W6bn7RDrPopGojU9sivphzGakcFSX14GmBIAkNM z5CffWDpc3drgPtGPx6OSUz3GxR3pPS0jVdlLCwjmBBqQzr6Kce8zsaXvfbZ4UW1hWv1 FtOhqmIye2FeBEaMqwVSkYOv5502D+SIsf9dXvJ2Iwk6L+sAP29ksvQyeH6iN257uDqN XZAXxcL9Eg2SZxf8EmFFT2fUH/BMB9PuC3gBhop+AiYX0Zrnr8wIWATfGFnq5gZmwmOO UTTeieZcL3kxpa1HDiLOYDOR/bwMgWKNKbH4tEIicm2C7LyXRx5g1hznQBLmXbZ04f+C ibmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725569496; x=1726174296; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FGoMR4Rh2+I0F+KnAtAj4qDB1TwB5zXtDQwb8przRbI=; b=J/x9R7kcR264DgDOfnivDAk9Z1pHq8htu0lmK5DCmKDMOl08bXZjUSDJY2GLaRVypx 2EZR7uAZ9iomt+qLUsiJnm/Gd95PxHpjBVLGLAPTpTiI2/67+V0n2ucqoyGZPhEVw6Ah qfDe8E+RX/gz+cNTd/XWO62NxUdHEuemG8Aj3zhVnOIiFvg/24YFimInyuU7TnvDPr+K 0+DcY23oSY9Ph5It6kwJwOXr/iLKy1ksGRRO0TbxlzPI7k9KWqVXglh+fQ/MeuH35Fy0 lot9w9nD1L16bTP9BBkLbatbPWSkS88Znw+KfT5akBGZqvavaOD5ZcZgCgT/N6W8DnHP 0E/Q==
X-Forwarded-Encrypted: i=1; AJvYcCWalmgsHUzVvLe3OYYMhCAQ9Xap3g7wekFkVBOhDrlRdTTkw6KS4IK3eNQyVIKByMgGGRq27YVEpA==@ietf.org
X-Gm-Message-State: AOJu0YyKFGLl6RMoHY83YjA3AW4BDc5al1gCIrWEZG1rsxlFfP7MHR2v /6bOqWAGTY7D7HDQbDudF7pR8KvuJCy0p5XTXJ0720GAM/ifo1eh+CnsHn7f644GRBdCqvp5SUA =
X-Google-Smtp-Source: AGHT+IFQPx5tacCoHlw0F89NRjrOR2hN8L5KDUDrLeCgfywaRv6hBIBv+bvYkdKOdJIkZt2JU+1lyw==
X-Received: by 2002:a05:6122:470f:b0:4f5:2276:136d with SMTP id 71dfb90a1353d-50207bfad10mr424290e0c.1.1725569496324; Thu, 05 Sep 2024 13:51:36 -0700 (PDT)
Received: from mail-ua1-f52.google.com (mail-ua1-f52.google.com. [209.85.222.52]) by smtp.gmail.com with ESMTPSA id 71dfb90a1353d-501299441c6sm73466e0c.8.2024.09.05.13.51.35 for <wgchairs@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Sep 2024 13:51:35 -0700 (PDT)
Received: by mail-ua1-f52.google.com with SMTP id a1e0cc1a2514c-846cdfbb153so341631241.0 for <wgchairs@ietf.org>; Thu, 05 Sep 2024 13:51:35 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCUTAjIo1wDc6A+h+iQekkZY9omAR6o5w6kR9OwaKgrIBFILF4hlLVZ8wHJaXBgo0Kwbyg9wvv8hEg==@ietf.org
X-Received: by 2002:a05:6102:3a12:b0:492:773e:a362 with SMTP id ada2fe7eead31-49bde2e2a43mr409953137.25.1725569495514; Thu, 05 Sep 2024 13:51:35 -0700 (PDT)
MIME-Version: 1.0
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> <ZtoYz78OBV5F0T7Z@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <ZtoYz78OBV5F0T7Z@faui48e.informatik.uni-erlangen.de>
From: Aaron Parecki <aaron@parecki.com>
Date: Thu, 05 Sep 2024 13:51:24 -0700
X-Gmail-Original-Message-ID: <CAGBSGjps-KLGJbJst_a2DykCe8DLaZGFtj1T5xX0_MmvLN1wxQ@mail.gmail.com>
Message-ID: <CAGBSGjps-KLGJbJst_a2DykCe8DLaZGFtj1T5xX0_MmvLN1wxQ@mail.gmail.com>
Subject: Re: System generated chat messages during WG sessions
To: Toerless Eckert <tte@cs.fau.de>
Content-Type: multipart/alternative; boundary="000000000000d0e69d06216574ed"
Message-ID-Hash: EOPMERFPIM4HCYXFCSL5KRKV22TVCGMQ
X-Message-ID-Hash: EOPMERFPIM4HCYXFCSL5KRKV22TVCGMQ
X-MailFrom: aaron@parecki.com
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: "Andrew G. Malis" <agmalis@gmail.com>, 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/Dg4oLd4-kXP3YeTidMS3GD4apVY>
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>
I find it extremely helpful to have at least a division in the chat between presentations. I've sometimes done this manually for meetings I'm in, typing out a row of "---------" and then the new presentation name. Even when live, just trying to scroll back up through the chat can be challenging to see when you've reached the top of the chat for the current session, so these markers can be helpful. I agree that noting every slide change would be a bit overkill though. On Thu, Sep 5, 2024 at 1:47 PM Toerless Eckert <tte@cs.fau.de> wrote: > 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 > >
- System generated chat messages during WG sessions Jay Daley
- Re: System generated chat messages during WG sess… Jeffrey Haas
- Re: System generated chat messages during WG sess… Gorry Fairhurst
- RE: System generated chat messages during WG sess… bruno.decraene
- Re: System generated chat messages during WG sess… Aaron Parecki
- RE: System generated chat messages during WG sess… Susan Hares
- Re: System generated chat messages during WG sess… Andrew G. Malis
- Re: System generated chat messages during WG sess… Toerless Eckert
- Re: System generated chat messages during WG sess… Andrew G. Malis
- Re: System generated chat messages during WG sess… Toerless Eckert
- Re: System generated chat messages during WG sess… Andrew G. Malis
- Re: System generated chat messages during WG sess… Robert Sparks
- Re: System generated chat messages during WG sess… Toerless Eckert
- Re: System generated chat messages during WG sess… Aaron Parecki
- Re: System generated chat messages during WG sess… Toerless Eckert
- Re: [irsg] System generated chat messages during … Carsten Bormann