{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/battery/issues/5","repository_url":"https://api.github.com/repos/w3c/battery","labels_url":"https://api.github.com/repos/w3c/battery/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/w3c/battery/issues/5/comments","events_url":"https://api.github.com/repos/w3c/battery/issues/5/events","html_url":"https://github.com/w3c/battery/issues/5","id":164335131,"number":5,"title":"Permission model & potential privacy-invasive usage","user":{"login":"anssiko","id":765510,"avatar_url":"https://avatars.githubusercontent.com/u/765510?v=3","gravatar_id":"","url":"https://api.github.com/users/anssiko","html_url":"https://github.com/anssiko","followers_url":"https://api.github.com/users/anssiko/followers","following_url":"https://api.github.com/users/anssiko/following{/other_user}","gists_url":"https://api.github.com/users/anssiko/gists{/gist_id}","starred_url":"https://api.github.com/users/anssiko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anssiko/subscriptions","organizations_url":"https://api.github.com/users/anssiko/orgs","repos_url":"https://api.github.com/users/anssiko/repos","events_url":"https://api.github.com/users/anssiko/events{/privacy}","received_events_url":"https://api.github.com/users/anssiko/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-07-07T15:18:57Z","updated_at":"2016-10-07T12:28:19Z","closed_at":null,"body":"Starting with a concern raised in https://lists.w3.org/Archives/Public/public-device-apis/2016Jul/0000.html (see the full thread), we ended up discussing the permission model for the API, in particular why it is different from other APIs.\r\n\r\nLet's use this issue to document proposed solutions that could be transformed into spec prose, while keeping compatibility with the existing shipping implementations."},"comment":{"url":"https://api.github.com/repos/w3c/battery/issues/comments/252239648","html_url":"https://github.com/w3c/battery/issues/5#issuecomment-252239648","issue_url":"https://api.github.com/repos/w3c/battery/issues/5","id":252239648,"user":{"login":"lknik","id":13951853,"avatar_url":"https://avatars.githubusercontent.com/u/13951853?v=3","gravatar_id":"","url":"https://api.github.com/users/lknik","html_url":"https://github.com/lknik","followers_url":"https://api.github.com/users/lknik/followers","following_url":"https://api.github.com/users/lknik/following{/other_user}","gists_url":"https://api.github.com/users/lknik/gists{/gist_id}","starred_url":"https://api.github.com/users/lknik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lknik/subscriptions","organizations_url":"https://api.github.com/users/lknik/orgs","repos_url":"https://api.github.com/users/lknik/repos","events_url":"https://api.github.com/users/lknik/events{/privacy}","received_events_url":"https://api.github.com/users/lknik/received_events","type":"User","site_admin":false},"created_at":"2016-10-07T12:28:19Z","updated_at":"2016-10-07T12:28:19Z","body":"Let's add at the consideration's end:\r\n\r\n> The information provided by Battery API may potentially be used in profiling the user via analysis of device use patterns.\r\n\r\n(I don't think we should link to any media reports/blogs and mentioning media posts in the spec are probably not good practices?) \r\n\r\nWe can also consider changing MAY to SHOULD, so rephrase:\r\n\r\n> The user agent MAY ask the user for battery status information access, or alternatively, enforce the user permission requirement in its private browsing modes. \r\n\r\nto:\r\n> The user agent SHOULD be subject to permissions \r\n"}}
{"actor":{"display_login":"lknik"}}