Re:How we built a GDPR-compliant website analytics platform ...
by abtestdev on Monday July 22, 2019 @10:46AM
(#20498446)
How do you guard against hash collision?
[ Parent
| on HN ]
Re:How we built a GDPR-compliant website analytics platform ...
by JackWritesCode on Monday July 22, 2019 @10:52AM
(#20498515)
Re:How we built a GDPR-compliant website analytics platform ...
by abtestdev on Monday July 22, 2019 @11:05AM
(#20498662)
Based on the blog - anyone who shares a IP address (such as inside a company network) would effectively look the same.
Re:How we built a GDPR-compliant website analytics platform ...
by proaralyst on Monday July 22, 2019 @11:17AM
(#20498789)
And given most companies run managed browsers on managed systems, the user agent is going to collide too
Re:How we built a GDPR-compliant website analytics platform ...
by _-___________-_ on Monday July 22, 2019 @04:38PM
(#20502106)
Not just inside a company network. CGNAT is pretty commonplace nowadays.
Re:How we built a GDPR-compliant website analytics platform ...
by JackWritesCode on Monday July 22, 2019 @11:17AM
(#20498809)
Indeed. This is one of the limitations to our approach. We're thinking of ways to workaround it. Please shout if you have any ideas ;)
Re:How we built a GDPR-compliant website analytics platform ...
by cameronbrown on Tuesday July 23, 2019 @04:25AM
(#20505261)
If/When IPv6 is widely used the problem should fade away.