How Bungie identified a mass sender of fake DMCA notices

Re:How Bungie identified a mass sender of fake DMCA notices by ta988 on Friday June 24, 2022 @11:01PM (#31872121)

Store it because nobody knows what to do with it?

[ Parent | on HN ]

Re:How Bungie identified a mass sender of fake DMCA notices by woojoo666 on Friday June 24, 2022 @11:57PM (#31872459)

That's the optimistic case I guess. But I've already given an example where I suspect Google used timing analysis to figure out a youtube video that I watched (over VPN and using a FOSS youtube client). I think it's plausible that Google is already using timing analysis to track users

[ Parent | on HN ]

Re:How Bungie identified a mass sender of fake DMCA notices by iamacyborg on Saturday June 25, 2022 @02:56AM (#31873169)

That would explicitly not be in line with the GDPR. Specifically, it would break 5.1(b) - purpose limitation.

> collected for specified, explicit and legitimate purposes

[ Parent | on HN ]

Re:How Bungie identified a mass sender of fake DMCA notices by scrollaway on Saturday June 25, 2022 @03:06AM (#31873210)

Data about logged in sessions is generally stored for security purposes.

If a malicious person had access to your account you want to know for how long they had that access for example.

[ Parent | on HN ]

Re:How Bungie identified a mass sender of fake DMCA notices by iamacyborg on Saturday June 25, 2022 @03:27AM (#31873297)

Sure, that seems like it’d be a legitimate purpose, my comment was more a response to this.

> Store it because nobody knows what to do with it?

[ Parent | on HN ]