4 ms·
Here it is on the wayback machine for EU users getting a 451 error. https://web.archive.org/web/20190322180054/https://www.bakersfield.com/ap/national/living-o
by jasoncartwright 8y ago
Here it is on the wayback machine for EU users getting a 451 error.
https://web.archive.org/web/20190322180054/https://www.bakersfield.com/ap/national/living-on-pennies-with-a-million-dollar-view-how-car/article_edf4971c-045a-5265-b772-b857df180d4b.html https://web.archive.org/web/20190322180054/https://www.baker...
- isostatic 8y agoSo either 1) They are targetting EU users and serving to EU users and thus the block is pointless 2) They aren't targetting EU users and thus the block is pointless
- tzs 8y agoOr (1) they aren't sure if they would count as targeting EU users, because the rules are fuzzy and might be interpreted differently by each country's regulators, and (2) they don't have any need to target EU users since their content, and their monetization, is mostly of interest to non-EU users. In that situation, there are two cautious ways to proceed. One approach is to assume that you might be targeting EU users and so comply with GDPR. Even if you aren't doing anything with data that would make compliance hard, this is somewhat annoying because GDPR requires that you have a representative in the Union as a point of contact for users and regulators. The other approach is to make a good faith effort to block EU users. If you have little or no income directly or indirectly from EU users, the second approach has a lot to recommend it, especially until there is a good body of regulatory rulings on what GDPR actually means.