by ummjackson on 5/18/18, 3:37 PM with 51 comments
by salad77 on 5/18/18, 3:58 PM
I'm sure many Governments would love to be able to so simply identify what their citizens do online though.
by cpc26 on 5/18/18, 6:30 PM
by cpburns2009 on 5/18/18, 6:50 PM
> This tells nginx to assign the $allow_visit variable a 0 for any users the GeoIP database specifies as coming from the “EU” continent.
Europe is the continent. The EU does not encompass all European countries. Doesn't this needlessly block non-EU European countries?
by LinuxBender on 5/18/18, 5:24 PM
Just for fun, I would add
server {
# snip....
access_log off;
error_log off;
return 307 https://www.google.com/search?q=gdpr;
}
That should block anyone that might be a EU citizen. /sby ilovetux on 5/18/18, 9:16 PM
This, however, does give me an idea. Does anyone have an interest in a web framework which provides user/data management in a gdpr compliant way?
by lrpublic on 5/18/18, 8:38 PM
Assuming there is any significant adoption of your proposed solution to avoid GDPR rules the likelyhood is EU citizens will use VPN or Proxy services to bypass the restrictions.
I don’t think the use of a VPN would remove the GDPR obligations on the data controller or data processor.
by olliej on 5/18/18, 5:15 PM
by hathathat on 5/18/18, 5:24 PM
by splintercell on 5/18/18, 5:13 PM