News for hackers. Stuff that matters.
Re:Show HN - Client-side Google Analytics without using cookies by t0mas88 on Monday September 02, 2013 @04:49AM (#6314142)
This will not work in the Netherlands (although, see below, the law here might change soon). The law as written in NL prohibits reading data out of a user-device (fingerprinting) when not strictly necessary for delivering the service that was asked for. So getting things like screen-size and browser-name just for identification purposes is not allowed, because you wouldn't need those to deliver the service as requested by the user. Next to that, IP-addresses are under discussion for being "identifiable information", as is already the case in Germany.

Please do take this all with a grain of salt, because not a single website here actually adheres to the current implementation of the cookie-law. The political process has been set in motion to change the law and exempt anonymous statistics from the permission-requirements. This "soon to be exception" is already used by virtually all website and the regulatory agency responsible for enforcement seems to have decided not to make a problem of it for the time being.

Re:Show HN - Client-side Google Analytics without using cookies by mattront on Monday September 02, 2013 @09:30AM (#6315037)
Despite EU directive, cookie laws across EU differ quite a lot in terms of how they define acceptable/unacceptable use. I added the following notice to the original text to reflect this:

Use this code (GitHub) to implement client-side Google Analytics without storing data on user's device (cookies, cache, local storage, Etags...). The solution still uses the data from client devices to facilitate user tracking. Please check cookie laws of your individual country to see if you can legally use this approach without user opt-in.

Re:Show HN - Client-side Google Analytics without using cookies by bulte-rs on Monday September 02, 2013 @06:17AM (#6314417)
I think you're almost completely right on this one. Fingerprinting is allowed as long as it is a functional requirement of the website. What IS - to my best knowledge - unknown (or at least a gray area) is whether you can use a fingerprint created as a functional requirement for statistical purposes as an (double emphasis quote) "afterthought".