W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2016

Re: [sensors] Possibility of cross-domain communication using frequency in periodic reporting mode

From: Lukasz Olejnik via GitHub <sysbot+gh@w3.org>
Date: Sat, 25 Jun 2016 08:44:32 +0000
To: public-device-apis@w3.org
Message-ID: <issue_comment.created-228524398-1466844271-sysbot+gh@w3.org>
> @tobie 
> Now consider context C is no longer interested in getting sensor 
readings: A and B will get 200Hz.
> I can imagine you can use sensor frequency to transfer data between 
origins or across browsers by doing the following:
> Listener would set frequency to something low, say 50Hz. Emitter 
would use high and low frequency to transfer information (e.g. 800Hz 
for 1 and 200Hz for 0). You could even imagine the Listener peaking to
 1KHz to ack Emitter's message.

This is basically what I had in mind, that issue. Thanks. If there is 
even a potential possibility of this kind, we should address it in the
 considerations. I do not intend to hinder the work on the 
specification, in any way. What I am saying that if there is this 
possibility, we should include a remark in the considerations. I can 
definitely write one. I  think there might be a note specifying what 
happens in the situation with A, B, C - just to clarify how it works. 
I suggest including the other remark to privacy considerations 

I agree this may mostly relate  to low frequencies, but in general it 
is a good idea to write in a general form, for the general case of 
differentiation. And a very privacy-aware browser (think "tor mobile 
browser") might want to know about this.

In other words, I realize there are other techniques. What I am 
suggesting that we should just include it in the open - in the 
considerations section, especially since we are aware of such 

GitHub Notification of comment by lknik
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/100#issuecomment-228524398 using
 your GitHub account
Received on Saturday, 25 June 2016 08:44:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:33 UTC