Hacker News Reader

Comment by hvidgaard | Hacker News Reader

> It seems strange to me to have this enforcement of policies from countries that are not my own just because my website is accessible from those countries.

If you open shop in a different country, you follow their laws. Your website being accessible in a country is seen as the same thing. It's not hard to implement geo blocking if you want to show best effort and thereby opt out of it.

View on HN

This can very quickly become onerous for anyone wanting to run a website, if they have to understand the law of any country where it might be accessed. I think the onus of geoblocking should be in the country that decides this website doesn't obey it's laws, otherwise only large corporations with lawyers will be able to run websites.

If your website is doing business (i.e. Has some sort of legal presence) in another country, well, that's a different story.

If I'm just serving cat pictures, then I agree. But as soon as money and/or PII is involved, then a different set of rules apply.

This is where the technical complexity comes in. All of a sudden my static hosted page on github which gets a few hundred visitors per month and uses analytics should have Geo blocking? How much overhead will that add to the small site?

It's very unlikely your static page contains personal data that would be ok in the US but not in EU.

If you're referring to logging, there are some good responses in this discussion on how that will still be ok.

Reply on news.ycombinator.com