Re: [97attendees] meetecho from remote participant perspective

Sandra Murphy <sandy@tislabs.com> Tue, 15 November 2016 09:38 UTC

Return-Path: <sandy@tislabs.com>
X-Original-To: 97attendees@ietfa.amsl.com
Delivered-To: 97attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 338461297B8 for <97attendees@ietfa.amsl.com>; Tue, 15 Nov 2016 01:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 qYijyyyr-WQz for <97attendees@ietfa.amsl.com>; Tue, 15 Nov 2016 01:38:56 -0800 (PST)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F902129450 for <97attendees@ietf.org>; Tue, 15 Nov 2016 01:38:56 -0800 (PST)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 45C2228B003B; Tue, 15 Nov 2016 04:38:55 -0500 (EST)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id F090B1F8036; Tue, 15 Nov 2016 04:38:54 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_B9AAD837-3916-47EF-816F-713CB1038ECA"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <OGOFO1$B333B8EE7F0A98FEAD4BD582B7B39E69@meetecho.com>
Date: Tue, 15 Nov 2016 04:38:44 -0500
Message-Id: <51805921-CA3B-420A-8561-88F91F251AE5@tislabs.com>
References: <CAFgnS4XHZ2cRx1XD41vmnkohx_PjXLVj5RsoZEC=eyAvXV> <_umw@mail.gmail.com> <037f01d23f12$d0025> <260$7006f720$@olddog.co.uk> <17633600-> <6A04-4A2D-8DA8-BAF529A052ED@jisc.ac.uk> <CAFgnS4UN+W4z3_C4OvhJ7k8GJ-ysuEafcdFg0BVOts3h> <nKSjvw@mail.gmail.com> <D450F064.FA6F7%b> <rian.rosen@neustar.biz> <5CD4825B-7B42-4> <1C9-8640-5A95A3D4582A@jisc.ac.uk> <CA774> <99B-7739-47AA-9FA5-9E136869512B@tislabs.co> <m> <OGOFO1$B333B8EE7F0A98FEAD4BD582B7B39E69@meetecho.com>
To: ietf@meetecho.com
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/97attendees/s5m2E1QQr_xYOhhRJwnOmaBlwng>
Cc: 97attendees@ietf.org, Sandra Murphy <sandy@tislabs.com>, Tim.Chown@jisc.ac.uk, Adrian Farrel <adrian@olddog.co.uk>, Brian.Rosen@neustar.biz, dromasca@gmail.com
Subject: Re: [97attendees] meetecho from remote participant perspective
X-BeenThere: 97attendees@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Mailing list of IETF 97 attendees that have opted in on this list." <97attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/97attendees>, <mailto:97attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/97attendees/>
List-Post: <mailto:97attendees@ietf.org>
List-Help: <mailto:97attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/97attendees>, <mailto:97attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2016 09:38:58 -0000

> On Nov 15, 2016, at 4:28 AM, Meetecho IETF support <ietf@meetecho.com> wrote:
> 
> Hi Sandra,
> 
> if you're trying to join a jabber room with both your client and Meetecho using the same name, a conflict will indeed arise per the XMPP protocol specification.

So I guessed right for once.  Gee wiz.

> Meetecho handles this automatically by prompting you to choose a different name (e.g., Sandra Murphy 1), and I believe other clients do the same. If not, changing the display name there should fix it for you.

Guessing again - that Meetecho only does that if it is the one that starts second.

Good to know about the display name, I’ll look for a feature in my client.

> 
> As to following multiple sessions with Meetecho, you can do that as well. Just open different sessions in different browser tabs and you'll join them all at the same time.

Cool.  (Won’t the multiple audio feeds present a problem?  Or should I look for a meetecho knob that mutes the audio in one session?)

—Sandy

> 
> Hope this helps,
> the Meetecho Team
> 
> 
> 
> From "97attendees" 97attendees-bounces@ietf.org
> To "Tim Chown" Tim.Chown@jisc.ac.uk
> Cc "Dan Romascanu" dromasca@gmail.com,"RosenRosen, Brian" Brian.Rosen@neustar.biz,"97attendees@ietf.org" 97attendees@ietf.org,"Adrian Farrel" adrian@olddog.co.uk,"Sandra Murphy" sandy@tislabs.com
> Date Tue, 15 Nov 2016 03:26:18 -0500
> Subject Re: [97attendees] meetecho from remote participant perspective
> 
> Ah. In Adium, I am experiencing an error about unable to join group because of “conflict”. Some wg fail repeatedly, some work just fine.
> 
> I thought I detected a pattern of failure if I tried to join jabber for a wg I was watching in meetecho. Did you see the same?
> 
> With jabber I can follow multiple wg at the same time. I think that might be difficult to do in Meetecho?
> 
> (remote co-chair - neat! wish I’d thought of that.)
> 
> —Sandy
> 
> > On Nov 15, 2016, at 3:14 AM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
> >
> > My Jabber client has had significant problems connecting today. It was OK yesterday.
> >
> > I’ve not reported it though as Meetecho does everything in one view (chat, slides and video).
> >
> > Not sure about deprecating it, as Jabber + audio is a more lightweight way to participate remotely. Would be interesting to see the stats though.
> >
> > Tim
> >
> >> On 15 Nov 2016, at 08:05, Rosen, Brian <Brian.Rosen@neustar.biz> wrote:
> >>
> >> I don’t think that does anything. Meetecho uses jabber. It’s connected to our regular jabber server, using our normal rooms. Using the meetecho jabber client is certainly fine, but using any other jabber client works fine too, from our common server.
> >>
> >> Brian
> >>
> >> From: 97attendees <97attendees-bounces@ietf.org> on behalf of Dan Romascanu <dromasca@gmail.com>
> >> Date: Tuesday, November 15, 2016 at 3:00 AM
> >> To: Tim Chown <Tim.Chown@jisc.ac.uk>
> >> Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>uk>, "97attendees@ietf.org" <97attendees@ietf.org>
> >> Subject: Re: [97attendees] meetecho from remote participant perspective
> >>
> >> Should we consider deprecating jabber? I confess that I did not even bother launching my client, as the meetecho chat works so well.
> >>
> >> Regards,
> >>
> >> Dan
> >>
> >>
> >> On Tue, Nov 15, 2016 at 9:37 AM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
> >>> It’s very good.
> >>>
> >>> I suspect very few people are now using Jabber, with most joining directly to Meetecho. It would be interesting to see stats, if available.
> >>>
> >>> Tim
> >>>
> >>>
> >>>
> >>>> On 15 Nov 2016, at 07:35, Adrian Farrel <adrian@olddog.co.uk> wrote:
> >>>>
> >>>> I'd like to echo Dan's thanks.
> >>>>
> >>>> In the space of just a few meetings MeetEcho has gone from an experimental prototype to a regular and accepted part of the meetings.
> >>>>
> >>>> The only thing I find missing is that some chairs are unfamiliar with the system. We probably need to arrange a small amount of playing to get them over that hurdle.
> >>>>
> >>>> Adrian
> >>>>
> >>>> From: 97attendees [mailto:97attendees-bounces@ietf.org] On Behalf Of Dan Romascanu
> >>>> Sent: 15 November 2016 07:31
> >>>> To: 97attendees@ietf.org
> >>>> Subject: [97attendees] meetecho from remote participant perspective
> >>>>
> >>>> It's my first time using meetecho as remote participant. My experience is very good so far. I actually find it easier to make comments or ask questions as remote participant than in the room! Thursday I will co-chair a WG meeting remotely, let's see how this will work.
> >>>>
> >>>> Thanks to the team!
> >>>>
> >>>> Dan
> >>>>
> >>>> _______________________________________________
> >>>> 97attendees mailing list
> >>>> 97attendees@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/97attendees
> >>>
> >>>
> >>> _______________________________________________
> >>> 97attendees mailing list
> >>> 97attendees@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/97attendees
> >>>
> >>
> >> _______________________________________________
> >> 97attendees mailing list
> >> 97attendees@ietf.org
> >> https://www.ietf.org/mailman/listinfo/97attendees
> >
> > _______________________________________________
> > 97attendees mailing list
> > 97attendees@ietf.org
> > https://www.ietf.org/mailman/listinfo/97attendees
>