Re: [battery] Mitigating potential privacy-invasive usage

>I.e. to propose reporting of only certain levels, such as "low" 
"medium" "full", etc.

Mapping of "low", "medium", and "full" to implementation-specific 
`level` percentage values is a valid implementation strategy. 
@cpeterso also [suggested the 
same](https://twitter.com/cpeterso/status/792966620763213824).

>I'm also unsure about the real use cases for 
chargingTime/dischargingTime. How about (@anssiko ?) 
sanitizing/removing those or make them optional?

As the spec editor, I can't just remove features from the spec that 
are shipping. Implementers can make them less precise if they wish. 
Only if all the implementers agree, we can consider removing features 
from the spec.



-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at 
https://github.com/w3c/battery/issues/5#issuecomment-257854774 using 
your GitHub account

Received on Wednesday, 2 November 2016 12:49:14 UTC