This is a proposal regarding http://piwik.org/faq/general/#faq_43
There are cases where cookies are not supported either because the browser (user) has disabled them, or because the tracking code is running under the file:// protocol and not the http:// protocol. The latter case applies to following scenarios (among others):
In order to be able to produce unique visitor ids on the client and persist them on the client side, the HTML5 localStorage and sessionStorage could be used a a fallback mechanism.
The proposed flow inside piwik.js could be like this:
Keywords: cookies HTML5 localstorage sessionstorage
I'm not against this, but it's more complicated since we support opt-out. Side note: the evercookie proposal in #1725 was closed.
Using HTML5 localStorage does not break the opt-out mechanism. Instead of removing a cookie (or creating a no-track cookie) it can be that a localStorage variable that is created instead. Evercookie is by far a different approach. It creates a zombie cookie and it is not recommended for Piwik, I agree with you. All I'm suggesting is to have an alternative to store something on the client.
Thanks for the proposal. I like the idea!
How much code would this represent to be added to piwik.js? Would you submit such improvement?
hmm should we always store piwik identification directly on both places?
To make it redundant?
Maybe not by default but having to the possibility to activate it?