How a Diablo expansion led to behind-the-scenes trouble

Re:How a Diablo expansion led to behind-the-scenes trouble by Chris_Chambers on Sunday July 01, 2018 @02:31PM (#17436844)

GDPR requires you to “prove” you gained consent by creating a server-side timestamped log of the option each user chooses.

But you cannot see my comment because I was hellbanned, so enjoy wondering.

[ Parent | on HN ]

Re:How a Diablo expansion led to behind-the-scenes trouble by vertex-four on Sunday July 01, 2018 @05:39PM (#17437772)

The user is only given one option here, to accept tracking - the website isn’t even trying to be GDPR compliant, apparently they do not foresee having any EU visitors and so have no need to be. As a result, I’m not reading the damn thing.

[ Parent | on HN ]

Re:How a Diablo expansion led to behind-the-scenes trouble by polski-g on Sunday July 01, 2018 @06:57PM (#17438164)

Or a US company isn't going to comply with EU laws because they have no reason to.

[ Parent | on HN ]

Re:How a Diablo expansion led to behind-the-scenes trouble by vertex-four on Monday July 02, 2018 @06:22AM (#17440536)

If you make money off E.U. citizens, you should comply with E.U. laws. Simple as that. If you don’t want to comply with the laws of a country, do not make money off people there.

[ Parent | on HN ]

Re:How a Diablo expansion led to behind-the-scenes trouble by FreeFull on Sunday July 01, 2018 @02:52PM (#17436934)

I can see your comment, so maybe you aren't hellbanned any more.

[ Parent | on HN ]

Re:How a Diablo expansion led to behind-the-scenes trouble by grzm on Sunday July 01, 2018 @03:03PM (#17436984)

Users can vouch for dead comments which "reanimates" them. That may have been done in this case.

[ Parent | on HN ]