--On Wednesday, November 04, 2015 04:45 -0500 Kathleen Moriarty
<kathleen.moriarty.ietf@xxxxxxxxx> wrote:
> On Wed, Nov 4, 2015 at 4:12 AM, Randy Bush <randy@xxxxxxx>
> wrote:
>>> I'm sure many people working from home would not want their
>>> camera broadcasting them, and doubtless few other
>>> participants would welcome the view.
>
> I have tape over mine and just remove it when needed.
Yeah. I do something similar as protection against attacks that
could remotely activate the camera, but hope I never have to
treat Meetecho as an attack source. I also remember an earlier
generation of webcam devices that were equipped with a quite
obvious built-in physical lens cover or shutter arrangement and
regret the passing of that feature
> There was an issue where someone in meetecho has entered a Mic:
> comment and it was never said at a mic.
It was me; see below.
> I also was disconnected several times from the US, in MA, but
> it got better at the end.
I'm physically not far from you and got the same disconnections
(at least most of which were apparently at the Meetecho end --
see Simon's notes), but simply gave up after circa the third
one, shut the thing down and turned on the IETF audio feed and
logged into the Jabber room with a Jabber client. So I didn't
experience the "got better at the end" part. I also don't know
whether, with Meetecho acting up, its Jabber bridge/interface
was working -- most or all of the comments I saw in the Jabber
room after I connected directly seemed to be from people
directly logged into Jabber rather than via Meetecho with your
hum at the end as an exception.
Relative to the question I tried to ask via Jabber, my guess is
that Andrew and Jari were expecting questions to come in via
Meetecho, no one told them it was down or having problems, and
there was therefore no fallback plan such as a designated Jabber
scribe/channel who was logged directly into the Jabber room. I
tried getting the attention of a few people in the room or on
the stage to tell them about the problem and point folks to
questions in the chat room, but failed. Stuff happens, Murphy's
Law is still applicable, and it seems to me that one of the key
lessons from this experience is that we should get better at
assuming systems will fail and that we should have detection
mechanisms and fallbacks thought out and in place. In this
case, the audio feed and slides distributed before the meeting
were adequate, even if not very good, substitutes for Meetecho,
but the failure of the Jabber channel for questions to work was
a much more serious problem.
john