Re: [97attendees] meetecho from remote participant perspective

"Meetecho IETF support" <ietf@meetecho.com> Tue, 15 November 2016 09:29 UTC

Return-Path: <ietf@meetecho.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 2F2AB129524 for <97attendees@ietfa.amsl.com>; Tue, 15 Nov 2016 01:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aruba.it
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 k6hL7qvlS5mI for <97attendees@ietfa.amsl.com>; Tue, 15 Nov 2016 01:28:53 -0800 (PST)
Received: from smtpcmd01229.aruba.it (smtpcmd0648.aruba.it [62.149.156.48]) by ietfa.amsl.com (Postfix) with ESMTP id F2D82129A5A for <97attendees@ietf.org>; Tue, 15 Nov 2016 01:28:52 -0800 (PST)
Received: from meetecho.com ([62.149.158.90]) by smtpcmd06.ad.aruba.it with bizsmtp id 89Up1u00S1xJdJu019UpV1; Tue, 15 Nov 2016 10:28:51 +0100
Date: Tue, 15 Nov 2016 10:28:48 +0100
Message-Id: <OGOFO1$B333B8EE7F0A98FEAD4BD582B7B39E69@meetecho.com>
In-Reply-To: <CA77499B-7739-47AA-9FA5-9E136869512B@tislabs.com>
References: =?iso-8859-1?q?=3CCAFgnS4XHZ2cRx1XD41vmnkohx=5FPjXLVj5RsoZEC=3DeyAvXV?= =?iso-8859-1?q?=5Fumw=40mail=2Egmail=2Ecom=3E_=3C037f01d23f12=24d0025?= =?iso-8859-1?q?260=247006f720=24=40olddog=2Eco=2Euk=3E_=3C17633600=2D?= =?iso-8859-1?q?6A04=2D4A2D=2D8DA8=2DBAF529A052ED=40jisc=2Eac=2Euk=3E_?= =?iso-8859-1?q?=3CCAFgnS4UN=2BW4z3=5FC4OvhJ7k8GJ=2DysuEafcdFg0BVOts3h?= =?iso-8859-1?q?nKSjvw=40mail=2Egmail=2Ecom=3E_=3CD450F064=2EFA6F7=25b?= =?iso-8859-1?q?rian=2Erosen=40neustar=2Ebiz=3E_=3C5CD4825B=2D7B42=2D4?= =?iso-8859-1?q?1C9=2D8640=2D5A95A3D4582A=40jisc=2Eac=2Euk=3E_=3CCA774?= =?iso-8859-1?q?99B=2D7739=2D47AA=2D9FA5=2D9E136869512B=40tislabs=2Eco?= =?iso-8859-1?q?m=3E?=
MIME-Version: 1.0
X-Sensitivity: 3
Content-Type: multipart/alternative; boundary="_=__=_XaM3_.1479202129.2A.433885.42.27432.52.42.007.731629638"
From: "Meetecho IETF support" <ietf@meetecho.com>
To: sandy@tislabs.com
X-XaM3-API-Version: V3(R2)
X-SenderIP: 31.130.230.78
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1479202131; bh=I8QCbiOAqkJ+NOWvtoFxzAVD2wQqA1cNrFl+MEW4YvI=; h=Date:Subject:MIME-Version:Content-Type:From:To; b=EM567AMi/G/OmnJ/bLl0CJEHEmMEaujItVTeI34d9Tb+VSfP6G5DYSe2FhArALLZ4 zdPSj2iNIfZL6ispNob2g3M1vRd2ishkbhhLTxnA0KOWpoPDON22yL5B9zQ3e5Qlv3 5LF4mPTOHQMpZC/WsuN61EU8sVr0GkA+No6tGKonzPCj73el0Eac5bPLuBvurN0/Ip 7YGz5c8xFTyFZCxPrs3j3dmGKgNrNM7JyYNvHDU6TIsIPofXBtxT1u0baPFIR6FzNR 1JEehBuIKm8HdW0a+rUObbaLB49uBBlHm7WtJTHWxW62Cd5FCT5MNrcwfw+ScFlnmS jqbmPlwbnHXeg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/97attendees/FL-E2F7mIuyAbi6lI2YqL_30lmA>
Cc: 97attendees@ietf.org, sandy@tislabs.com, Tim.Chown@jisc.ac.uk, 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
Reply-To: ietf@meetecho.com
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:29:03 -0000

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