>One way you could get around this issue (although still not 100% foolproof) is browser fingerprinting. Your identity is the hash of your browser fingerprint.

>One way you could get around this issue (although still not 100% foolproof) is browser fingerprinting. Your identity is the hash of your browser fingerprint. Congratulations. You just conflated the user-agent for the user. Stop. Doing. That. People are flesh and blood. Browser fingerprints are bundles of configuration and hardware quirks, that if we actually implemented browsers correctly, would not even allow you access to half the API's that are otherwise exposed without actively notifying the user and asking the user for permission while making it clear that most of said activity is essentially a way to offload computation burden for the "developer's" benefit.