W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > March 2016

Re: [mediacapture-main] Persist device IDs like they were cookies,

From: Martin Thomson via GitHub <sysbot+gh@w3.org>
Date: Mon, 14 Mar 2016 04:41:17 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-196136091-1457930476-sysbot+gh@w3.org>
Let's go through the list (is it exhaustive?):

* visibility - sure; UA problem
* tool/extension support - sure; again, UAs need to handle that, which
 could be addressed by storing them like cookies
* expiry - not relevant; maximum cookie lifetime is effectively 
* third-party blocking policies - I'm not 100% on the details here, 
but I believe that this only applies to httpOnly cookies; if it 
doesn't, then (as implementers who enabled this unstandardized 
feature) we should do whatever DOM local storage, or indexedDB, or 
<raft of other stateful features>
* laws - I should say this, but I will; laws that identify cookies and
 assign them some sort of special status over all of the myriad other 
ways in which tracking might be enabled in a browser are daft

Yes, device identifiers are not cookies.  They are less capable than 
cookies.  They also have less baggage than cookies.

However, if you want to take on the crusade against origin-bound, 
persistent state in the browser, I'd suggest that this isn't the hill 
upon which to die.  Take them all on and work out how you might 
properly manage state.

GitHub Notification of comment by martinthomson
Please view or discuss this issue at 
 using your GitHub account
Received on Monday, 14 March 2016 04:41:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:29 UTC