3 ms·

I'm not sure if I missed some other explanation around IP addresses, but aside from rotating IPs from ISPs this would have trouble in shared networks where peop

I'm not sure if I missed some other explanation around IP addresses, but aside from rotating IPs from ISPs this would have trouble in shared networks where people use the same browser and/or OS so the IP and agent string would be the same. Say, an office or home network. Any way around this using other data perhaps? Not dissing, just curious as to the server analytics space atm. With Chrome taking most browser traffic and Windows for desktop OS (Android on mobile, globally) there may be frequent false positives as such. Best next assumption as a "solution" is that one wouldn't expect all network users to visit the same site :p

marvinblum 6y ago
You can compensate for it a bit by reading the X-Forwarded-For header. In case someone sits behind a proxy, they usually set this header with the actual IP address of the client. You can see this here: https://github.com/emvi/pirsch/blob/master/fingerprint.go#L29 https://github.com/emvi/pirsch/blob/master/fingerprint.go#L2...
- gnabgib 6y ago
  Behind a proxy that is (optionally) configured to share this - yes. But what of a NAT[1] gateway.. most home (and many business) networks NAT your connection - to the destination server, all devices in that network have the same IP (or the IP is seemingly very dynamic if measuring hash(agent+ip)). Other than a server or a mobile-device on network data (assuming they aren't using IPv6) an IP will almost always represent a cluster of devices. [1]: https://en.wikipedia.org/wiki/Network_address_translation https://en.wikipedia.org/wiki/Network_address_translation
  - marvinblum 6y ago
    Hard to tell how often that happens. The User-Agent should help a lot with that. I will collect more data and try to figure out how well it really works.