Hacker News Reader

Those fingerprints are mostly based on information that your browser gives out voluntarily for no good reason (the server doesn't need to know your fonts, screen resolution, plugins or user-agent).

Thus an easy workaround would be to use a plugin that randomizes all this, which turns your one unique identity into many unique identities.

View on HN

user-agent is most definitely needed. My server gives different content depending on which kind of client accesses the page and I certainly don't want to do that in javascript.

Then your server is broken. That's what the "accept*" headers are for.

Accept headers are going to tell me what CSS bugs are present?

That's what conditionals inside the CSS are for.

Browser sniffing simply doesn't work and only brings you pain. Enough so that jquery abandoned the practice a year ago; http://docs.jquery.com/Release:jQuery_1.3

Reply on news.ycombinator.com