Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7FB9E200B34 for ; Sat, 18 Jun 2016 00:16:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7E3E0160A62; Fri, 17 Jun 2016 22:16:44 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C2856160A61 for ; Sat, 18 Jun 2016 00:16:43 +0200 (CEST) Received: (qmail 33972 invoked by uid 500); 17 Jun 2016 22:16:42 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 33960 invoked by uid 99); 17 Jun 2016 22:16:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2016 22:16:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 2C48FC0DF1 for ; Fri, 17 Jun 2016 22:16:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 0IZdohXLFDXA for ; Fri, 17 Jun 2016 22:16:40 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id BB3165F574 for ; Fri, 17 Jun 2016 22:16:39 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id s186so100173529qkc.1 for ; Fri, 17 Jun 2016 15:16:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=kpDUttxYHaMt6qcPmP1dAD8FNVNDpyAaRr+ZkoqBko4=; b=sIttzvzXItvI/HcwnRNNs1AtEB5vNWGFhMyvIZMV2lE5o4aURv1wqiYhYEjlMNRYrd 4ALDw2W7ywjPqBa/Vgm61LlkDsl5vZ1FV4707ngJRAhah/64kTIGIf6GONh2vGNM0pJg jHfnx+kh7p4+yLHqJjJxjcLVmXVdopEs9ljyODNSnG2nDwYaOuFQIU6c+9IBOXf/izBw 5qYmLtjsABNt9yFle1BdMod82w4lEsXoIcUmmqvrrjf2RxzJBwBcOAXM5Z00nRWm/xIE 8N+CWF+QgEw9+55gdTE7yXnXgBOthltUhzyXdMAMx+DcUoqf/nMWJ5+4KdTi9oLICesL 1FJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=kpDUttxYHaMt6qcPmP1dAD8FNVNDpyAaRr+ZkoqBko4=; b=XmN9VlXGuOKgvUdP1ZUZoDQP4xDU66yUl9MO6VStja6JSRkDG6YRFQRjJB4TFldUxr JV6qzyjg3YX84ojqOcZKbnZbbU9nW/EdzBrf2vgKsrt2N9dv3w4aNJI+htp232d6NOuW 4JDEn+zw4K6GfA48A0sqgWjbST0iAhaZ+abHvLgvtmk0L4zdYXcCgjoRDoW3c3GkFfWT ZOQiZUveOlbxYOnD/lNwyt6pE/PSpaTSXI3kn3mVlfw8CiLQQjRX+JBYu7K5NoZNMeEg 06E9YZXHkNoY1lQsZSPWsicKI1j1x9VDMcU1Dv4UdLVjffl+XjM0PS2Xk9veeUT5phDk yYXQ== X-Gm-Message-State: ALyK8tJkE1RSGj36LhyDQDoWensad8eIPnXHtLJR8w1+8QS5635mWI8Vv2wa09KhQlM7ypQr4r3x0EpZjS67SQ== X-Received: by 10.200.54.59 with SMTP id m56mr5543293qtb.87.1466201793640; Fri, 17 Jun 2016 15:16:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.80.139 with HTTP; Fri, 17 Jun 2016 15:15:54 -0700 (PDT) In-Reply-To: References: From: Shazron Date: Fri, 17 Jun 2016 15:15:54 -0700 Message-ID: Subject: Re: [Discuss] Why was device.name removed from the device-plugin? To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=001a113c786c143fc0053580b530 archived-at: Fri, 17 Jun 2016 22:16:44 -0000 --001a113c786c143fc0053580b530 Content-Type: text/plain; charset=UTF-8 I have no objection if the API property is unambiguous, unlike what it was before (over 4 years ago!), and is supported by all the major platforms (looks like it is, from what you mentioned). Also -- Ubuntu/Linux looks like its just /etc/hostname. We'll just have to bump a minor version. What do the others think? On Fri, Jun 17, 2016 at 3:07 PM, Philipp Kursawe wrote: > To further emphasize one point. I fully agree with moving from device.name > to device.model + device.manufacturer + device.platform. > But I still ask all of you do consider bringing back a proper device.name. > As I wrote, on Windows its pretty easy to get the real name of the > PC/Phone. On iOS and Android the work is already done. > > On Sat, Jun 18, 2016 at 12:02 AM, Philipp Kursawe > wrote: > > > Thanks for pointing this out. However the name is not used to reference > > the device to the API. Thats what the device.uuid is being used for. The > > device name is used in the UI where the user can see its API enabled > > devices. You don't want to show the user the device id there (cause she > has > > no point of reference to which physical device it belongs) but the name > she > > gave her phone and knows her phone when she connects it to itunes, iphoto > > etc. > > > > So the reason to introduce the name property back is exactly the one you > > mentioned: The user can always change the name of her phone and there > knows > > its name and will recognize it in a list of devices. > > > > On Fri, Jun 17, 2016 at 9:23 PM, Shazron wrote: > > > >> Hi Philipp, > >> This was the rationale: > >> > >> > https://lists.apache.org/thread.html/e3b0e5f87ba3929d5578308b25ee9a6af5b91177b94015878970fa8e@1352248856@%3Cdev.cordova.apache.org%3E > >> > >> On iOS, [UIDevice name] returns the name the user sets in iTunes for > >> their > >> device i.e. "Shazron's iPhone 4", and can change anytime so relying on > it > >> for API access would be problematic. > >> > >> > >> On Fri, Jun 17, 2016 at 1:51 AM, Philipp Kursawe < > phil.kursawe@gmail.com> > >> wrote: > >> > >> > I wonder why such an important piece of information is not provided > >> anymore > >> > in the device plugin? > >> > What was the reason to remove the property? > >> > > >> > The name of the device, especially when users can authorise/revoke API > >> > access to apps on different devices, is an important variable to know. > >> > > >> > There is a plugin that brings back this functionality for Android, iOS > >> and > >> > for Windows it would be a one-liner only too. > >> > https://github.com/becvert/cordova-plugin-device-name > >> > > >> > > > > > --001a113c786c143fc0053580b530--