3 ms·
One approach would be for browsers to send a string that is along the lines of a uuid generated at compile time, or an MD5 of the executable. That way, analyti
by tacostakohashi 12y ago
One approach would be for browsers to send a string that is along the lines of a uuid generated at compile time, or an MD5 of the executable.
That way, analytics vendors or libraries could maintain a database that maps IDs to specific browsers releases, platforms, features, etc if they care about those things enough, but short-sighted web admins would have no hope of doing anything with primitive regex matching of the UA string.
- firepacket 12y agoYou mean a super cookie? Not only would this violate tracking laws in some areas, but who would ever want to use such a thing?
- tacostakohashi 12y agoNo. Generated at the time the browser executable is built (by the vendor, linux distro, etc), and hence shared by all the people using that browser executable. So, only good for identifying the browser, platform, OS and features, and much less so the users.
- tracker1 12y agoYou're welcome to do just that.. md5(useragent) and keep your own definitions... be mindful that in IE in particular plugins affect the string itself. :-(