181–190 of 231 posts
So if you're using something like a pihole, and provided you're not using any of the mentioned companies, your go to go?
Alternative title: French courts order American DNS providers to block unlicensed sports streaming websites.
Your claim would make sense if they had no operations in France, but I highly doubt that's the case. If you operate in those countries, you have to comply with their laws. The fact that your company is incorporated elsewhere is irrelevant.
Alternative title: French courts order American DNS providers to block unlicensed sports streaming websites.
*American multinationals Your claim would make sense if they had no operations in France, but I highly doubt that's the case. If you operate in those countries, you have to comply with their laws. The fact that your company is incorporated elsewhere is irrelevant.
Earlier quoted context omitted.
Fixed now, although leaving out the court order is also misleading. If anyone wants to suggest an accurate, neutral title that gets it all under the 80 char limit, we can change it again.
Asked ChatGPT, it came up with this Court Orders Google, Cloudflare & Cisco to Poison DNS to Stop Piracy
If you need to poison the DNS by court order. Can you also just poison the requestees DNS entries? E.g. Canal+ own websites?
Childishness aside, this is a dumb idea because it's going to piss off more users than appease. Most don't care about the struggle for internet freedom or whatever, and just want their sites to work. For them blocking legitimate sites a sign that their ISP is broken, especially when their friends/colleges report that it's working fine on their connections. Moreover blocking illegal streaming sites is court sanctioned…
Earlier quoted context omitted.
Tech has always been part of the establishment, funded by capital trying to solve capital's problems. The only part of tech that really deviates from this is the free software community, which has always been hostile to capital. The blackout day emerged from people, not the industry, and people have changed.
idunno, I remember when everything cool I found on the internet was on a .edu domain, because that's almost all there was. But yeah, capitalist tech has always been part of the establishment. A lot of the good stuff comes from non-profit-related motivations, fortunately.
root@jack:~# dig footybite.cc @8.8.8.8
; > DiG 9.18.19-1~deb12u1-Debian > footybite.cc
@8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADEREarlier quoted context omitted.
Or just footybite.cc will become footybite1.cc, then footybite2.cc... so on. The people writing these laws are seemingly clueless about the internet. Or perhaps, the lawyers just don't care as they are getting paid.
How will users find the new domains? If they can reliability do so then dns is not needed in the first place. If not, then the laws are effective.
Hell, they could setup their own public DNS outside of France and suggest users use that. Users already switched from local/ISP DNS to Cloudflare / Google because of the previous law so that is not a big hurdle (ignoring the obvious security problem - many users won't care they just want to watch the game).
My point though is that these laws will be very easy to bypass just like most anti piracy laws before it. Note that The Pirate Bay is still up and running.
Earlier quoted context omitted.
Logical extensions of this principle: * Domestic abuse is the victim's fault because they shouldn't have made their partner angry. * The Chinese GFW is the fault of the people who criticized the government. They shouldn't criticize the government. * Israel indiscriminately bombing Gaza is the fault of the Gazans who fought back the last time Israel did that. * The Holocaust is the Jews' fault for not fleeing the coun…
>* Domestic abuse is the victim's fault because they shouldn't have made their partner angry. * The Chinese GFW is the fault of the people who criticized the government. They shouldn't criticize the government. * Israel indiscriminately bombing Gaza is the fault of the Gazans who fought back the last time Israel did that. * The Holocaust is the Jews' fault for not fleeing the country sooner. Except in all those cases…
Earlier quoted context omitted.
> At this point, it is much easier to just block the service's IP addresses than deep-inspect DNS traffic and match the query identifier and stuff to inject a false response. Why spend that engineering time when people will just fix the DNS server and can access the site directly? Because IP addresses can change frequently, and also because if a site is behind a CDN, that would cause a lot of collateral damage. > The…
Could you give a example of such ISP? I have seen ISP block all DNS traffic beyond to their own server, but those have been fairly locked networks like hotel wifi. It is much cheaper, safer, and less fragile to just block everything and force customers to the isp own servers. DPI and traffic injection carries risk of false positives and minor engineering mistakes can create large support costs, and would really only…
Sure, that's common too. But that also precludes you from running your own recursive resolver to circumvent their blocks.