Re: [vmeet] IETF95 remote attendance

Meetecho IETF support <ietf@meetecho.com> Fri, 15 April 2016 17:22 UTC

Return-Path: <ietf@meetecho.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F11912E7A6 for <vmeet@ietfa.amsl.com>; Fri, 15 Apr 2016 10:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 zNrMngE4N_XZ for <vmeet@ietfa.amsl.com>; Fri, 15 Apr 2016 10:22:51 -0700 (PDT)
Received: from smtpcmd04134.aruba.it (smtpcmd04134.aruba.it [62.149.158.134]) by ietfa.amsl.com (Postfix) with ESMTP id EAF3412E754 for <vmeet@ietf.org>; Fri, 15 Apr 2016 10:22:49 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.134.3]) by smtpcmd04.ad.aruba.it with bizsmtp id ihNo1s01M04Zlvb01hNpNw; Fri, 15 Apr 2016 19:22:49 +0200
To: vmeet@ietf.org
References: <5710CA7F.3050207@meetecho.com> <5710CE07.9090104@gmail.com> <57110178.4030205@alum.mit.edu>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <57112363.7000105@meetecho.com>
Date: Fri, 15 Apr 2016 19:22:43 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <57110178.4030205@alum.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/vmeet/fepIc-qVheE7XHcqnIIz1zUV48s>
Subject: Re: [vmeet] IETF95 remote attendance
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2016 17:22:54 -0000

Il 15/04/2016 16:58, Paul Kyzivat ha scritto:
> On 4/15/16 7:18 AM, Stewart Bryant wrote:
>>
>>
>> On 15/04/2016 12:03, Meetecho IETF support wrote:
>>> - 712 unique remote participants joined Meetecho through the week;
>>> among these, 282 opted to also put their Registration ID.
>>
>> There was something odd about the registration number system.
>>
>> I tried to enter my registration number a few times but it rejected it
>> every time.
>>
>> Since it did not REQUIRE(sic)  the registration number  I just used the
>> option not to enter it.
>
> I understand how linking to the registration could be helpful. But the
> registration number isn't something that sticks in your memory. So I had
> to look up my registration confirmation and copy/paste the number. Doing
> that *once* wouldn't be much of a bother. But doing it for every session
> I entered was.
>
> I think we need to find a better system for this. Perhaps cookies could
> be used to remember this stuff for the duration of the week. Then at
> least it would only be necessary to enter it once per device.

This is definitely on our to-do list and will be implemented for the 
next meeting.

>
>      Thanks,
>      Paul
>
> _______________________________________________
> NOTE WELL: This list operates according to
> http://mipassoc.org/dkim/ietf-list-rules.html.
> https://www.ietf.org/mailman/listinfo/vmeet