zlacker

https://dash.cloudflare.com/?to=/:account/:zone/security/sec...

  (ip.src.country eq "GB")

then take action "Block". i know what you mean by a simpler option though

>>bstsb+(OP)
The point the parent is making is that you don’t have to manually keep track of the countries you need to block. You just tell Cloudflare what your website does / what type of laws may be problematic, and Cloudflare manages the blocklist automatically.

Makes a lot of sense actually that it’s surprising they don’t have this yet.

>>stingr+oj
So the entire internet goes off during La Liga?

>>stingr+oj
My guess is liability factor. If they get it wrong, massive liability on their side especially since someone could be like "I told you X" and Cloudflare didn't think the law applied or not.

Better to put onus on the customer.

>>stacks+sy
“”” Our analysis reports that the regulations that are currently being discussed and likely to have an impact on the following services of yours: {{SERVICES}}.

These regulations touch on the following points: {{POINTS}}.

Here are how each of your listed services would likely be impacted by the different components of the regulations:

- {{SERVICE}}

— {{POINTS}}

“””

>>stacks+sy
This is already a fact of life: Amazon, Cloudflare, etc all manage blocklists for common patterns in firewalls, and many compliance standards (e.g. SOC2) pretty much require you to enable them. Mistakes are sometimes made in these things, but fairly certain that liability is covered by the ToS.

>>lemonl+Wx
No? That's the other way around, ISPs blocking server IPs for customers. This is about servers blocking legally risky visitor IPs.