3 ms·

> they have to deal with the GDPR headache What headache? A sensible solution: when EU visitor is detected, don't set cookies. Purdue solution: when EU visito

> they have to deal with the GDPR headache What headache? A sensible solution: when EU visitor is detected, don't set cookies. Purdue solution: when EU visitor is detected, block them.

quartz 5y ago
> What headache? A sensible solution: when EU visitor is detected, don't set cookies. The headache is convincing someone to pay a lawyer to agree that this is the solution when serving content to the EU is outside your publication's mission. Also: The Exponent isn't Purdue, it's independent. Purdue chose email as their publication medium.
- hdjjhhvvhga 5y ago
  The GDPR is about personal data. It can get complex when you actually start to deal with personal data. You need to notify users, enable them to modify their data and so on. For many platforms this is already very easy or built in, for some like ERP systems it was quite complicated. Fortunately there exist a very simple solution: don't gather personal data. Note that it does not necessarily applies to cookies: they are considered personal data only if they can be used to identify the individual.[0] There is exactly zero chance anybody would go after you if you don't set cookies or set them for reasons other than making personal identification possible. [0] https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-cookie-policies https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-coo...
josefx 5y ago
Not sure if that is enough. They seem to have facebook and twitter links and as far as I remember these usually come in a JavaScript spyware bundle and those are only the obvious ones.
mikewarot 5y ago
>when EU visitor is detected, don't set cookies How do you know that somewhere in the stack of things the server is running isn't something that would set a cookie for some valid reason, and thus trigger the EU's stupid laws? A positive stop, the redirect to a text page, is far better than a hope and a prayer.
- hdjjhhvvhga 5y ago
  Not setting cookies is a radical solution. Actually there is no problem with cookies at all unless they are being used to identify the individual. [0] So by definition any valid reason causes absolutely no problem. It is only if you decide that you want to deal with personally identifiable information, transfer it to third parties etc., it becomes problematic. People in the EU quickly learned not to do that and we're very happy about it. [0] https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-cookie-policies https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-coo...
deleted 5y ago
[deleted]
PixyMisa 5y ago
Dealing with the GDPR costs money. Blocking the entire EU is free. This started happening even before the GDPR was finalised.

> they have to deal with the GDPR headache What headache? A sensible solution: when EU visitor is detected, don't set cookies. Purdue solution: when EU visitor is detected, block them.

quartz 5y ago

> What headache? A sensible solution: when EU visitor is detected, don't set cookies. The headache is convincing someone to pay a lawyer to agree that this is the solution when serving content to the EU is outside your publication's mission. Also: The Exponent isn't Purdue, it's independent. Purdue chose email as their publication medium.

hdjjhhvvhga 5y ago
The GDPR is about personal data. It can get complex when you actually start to deal with personal data. You need to notify users, enable them to modify their data and so on. For many platforms this is already very easy or built in, for some like ERP systems it was quite complicated. Fortunately there exist a very simple solution: don't gather personal data. Note that it does not necessarily applies to cookies: they are considered personal data only if they can be used to identify the individual.[0] There is exactly zero chance anybody would go after you if you don't set cookies or set them for reasons other than making personal identification possible. [0] https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-cookie-policies https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-coo...

josefx 5y ago

Not sure if that is enough. They seem to have facebook and twitter links and as far as I remember these usually come in a JavaScript spyware bundle and those are only the obvious ones.

mikewarot 5y ago

>when EU visitor is detected, don't set cookies How do you know that somewhere in the stack of things the server is running isn't something that would set a cookie for some valid reason, and thus trigger the EU's stupid laws? A positive stop, the redirect to a text page, is far better than a hope and a prayer.

hdjjhhvvhga 5y ago
Not setting cookies is a radical solution. Actually there is no problem with cookies at all unless they are being used to identify the individual. [0] So by definition any valid reason causes absolutely no problem. It is only if you decide that you want to deal with personally identifiable information, transfer it to third parties etc., it becomes problematic. People in the EU quickly learned not to do that and we're very happy about it. [0] https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-cookie-policies https://www.itgovernance.eu/blog/en/how-the-gdpr-affects-coo...

deleted 5y ago

[deleted]

PixyMisa 5y ago

Dealing with the GDPR costs money. Blocking the entire EU is free. This started happening even before the GDPR was finalised.