Re:Bear Does Analytics with CSS
by jakelazaroff on Wednesday November 01, 2023 @12:44PM
(#38100964)
My point is that your `wc -l access.log` solution will also track people who send the Do Not Track header unless you specifically prevent it from doing so. In fact, you could implement the exact same system described in the blog post by replacing the Python code run on every request with an aggregation of the access log. So what is the pragmatic difference between the two?
[ Parent
| on HN ]
From a technical point of view: The difference is that a CSS `body:hover` request excludes naïve bots, but an access log includes them. So it's more useful for the maintainer.
From a privacy point of view: The difference is that human usage won't blend in with bot traffic quite as easily, so they give up an amount of anonymity that most would probably consider inconsequential.
From an ethical point of view: In a deontological model of ethics, making someone's computer act against their interests is wrong, even if that harm is marginal. In a utilitarian model of ethics, making someone's computer act in that way is good, if the resulting data causes more good than the intrusion causes harm.
Even the GDPR makes this distinction. Access logs (with IP addresses) are fine if you use them for technical purposes (monitor for 404, 500 errors) but if you use access logs for marketing purposes you need users to opt-in, because IP addresses are considered PII by law. And if you don't log IPs then you can't track uniques. Tracking and logging are not the same thing.
Re:Bear Does Analytics with CSS
by jakelazaroff on Thursday November 02, 2023 @09:06AM
(#38112967)
May I remind you that your own suggested solution was using access logs for marketing purposes!