Mitigating this issue is a matter of filtering the readings from lower frequency `Sensor` objects at the expense of increased latency and CPU usage. Maybe the spec should be more explicit about this issue and carve the ability for a very privacy-aware browser to mitigate that threat at the expense of performance, but that would require first a clear understanding of the threat model. Given this new info, @lknik, could you please reassess the threat and compare it to other threats in the platform to see if it is worth dealing with? -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/100#issuecomment-228522768 using your GitHub accountReceived on Saturday, 25 June 2016 08:20:18 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:33 UTC