From the article:
Lots of automated traffic on the web, bots, crawlers and scrapers. So if there is a way that can remove most of the automated traffic without loading any JS, is that a win?
body:hover {
background-image: url("https://underjord.io/you-was-tracked.png");
}
[...] This has a certain elegance because it actually requires mouse interaction.That is not true. I just tried it with headless chrome and triggered :hover behavior immediately just by synthesizing mouse movement the same way I would by using it as a scraper.
You can use it to clean your analytics, but yes, it's useless for fraud prevention.
Sure, it'd clean analytics up a little bit, but that would come at the expense of being able to use a CDN/cache for my CSS. Even leaving aside implementation effort, that's a big price to get some but not all bots out of my log data.
And of course, if you share the data with a third party (that includes if you use their services to collect or process the data), you should logically assume the worst.
I would probably be okay to share all kinds of data with the websites I use, if I could reasonably trust that it will never be used to identify me personally. If you have a website, and you are curious whether your audience is mostly male or female, young or old, using computers or smartphones, I can understand the need, and would not object against my presence increasing some number in the database by one.
Well, there is this problem that if you collect too many attributes about me, and if they are all connected together (as opposed to merely increasing a few independent counters), a sufficiently large collection can be used in the future to identify me uniquely, which is the part I object against. And I have no control about how you store the information, and it is reasonable for me to assume the worst.
To make an analogy with the offline world, if you e.g. give a public lecture, you can see what kind of people are in the audience. And I would feel no desire to wear a mask for the purpose of hiding my age or gender or race or whatever from the lecturer.
But I would object against someone taking my photo, using it to identify me, and writing the information of me attending given lecture on given day into some huge dossier about me, that he would later share with other shady people, so that they can all have my incredibly detailed biography (in case of Google, including also most of my private correspondence). That is definitely evil.
It's making it personally identifiable and linking it to other things where you get in the really evil territory.
If it's CSS, then no.
If it's loading an external image, then also no. Certainly no more evil than any other method of getting a user's browser to make an HTTP request anyway.
If it's tracking users then maybe. Gathering data is evil unless you have a very good reason. If you're gathering it and not actually using it then that is definitely evil. If you're gathering everything in case you need it then that is also evil. If you're gathering data that's unique to individuals that's even worse. If you're gathering data that's unique to individuals, and keeping it, and using it to build up profiles by blending it with other sources, and then selling the information that's really evil.
Just gathering browser agent strings or screen resolutions though, it's not terrible. Although I do wonder why you need CSS analytics rather than just using the server log from the request for the HTML file.