3 ms·
That doesn't work anymore. ISPs are not going to block AWS IP ranges or Azure IP ranges, etc. The cloud killed IP blocking. The pirate bay is supposed to be blo
by mantap 7y ago
That doesn't work anymore. ISPs are not going to block AWS IP ranges or Azure IP ranges, etc. The cloud killed IP blocking. The pirate bay is supposed to be blocked in UK by court order, but because they use cloudflare it's still accessible and only DNS blocked.
- throw0101a 7y ago> ISPs are not going to block AWS IP ranges or Azure IP ranges, etc. Tell that to China, Iran, Turkey (?), etc.
- ru552 7y agoOk, authoritarian regimes not included
- throw0101a 7y ago> Ok, authoritarian regimes not included And yet this was/is one of the justifications for implementing this. They're not doing it in the EU because (a) there are decent privacy laws, and (b) IP addresses are (IIRC) considered personal information and so Cloudflare DoH would be responsible for keep a whole bunch of data safe. They may not want that responsibility. This seems to (currently) be US-only because of the sucky US privacy laws.
- mantap 7y agoNo the justification is to make it harder for non-authoritarian countries to block websites. If China or North Korea want to block the IP range of AWS+Azure+Google that's up to their respective autocrats. Most democratic or even hybrid regimes are not prepared for that level of absolute chaos and consequent protest if half the Internet is shut down. You can only pull that shit in a dictatorship.
- gsich 7y agoBlocking wasn't the point in the post above.
- mantap 7y agoOkay fair but they are two sides of the same coin. Blocking is active snooping. If an ISP knows what site you are visiting they can block the connection. In both cases the way to prevent it is to extinguish privacy leaks.