3 ms·

This feels much better than the Russian government's approach to censorship and modern tech. The problem is that there are people in Russian government who actu

This feels much better than the Russian government's approach to censorship and modern tech. The problem is that there are people in Russian government who actually have a clue about how this stuff works. If the blocking is done client-side, there's plenty of ways to bypass it, like just not updating your browser, duh. Or patching it, or installing extensions that neutralize the blocking mechanism, or fooling it into thinking you're in another country. Even if the blocking done via DNS, it's trivially bypassable by using a DNS provider that offers encryption. Russian approach, though, is to use deep packet inspection equipment (that doesn't implement the TCP spec, lol) to actively mess with people's connections to "forbidden" resources.

riedel 3y ago
I also do not quite get the GP comment. I see it also logical to block content on application layer from the OSI perspective. If you cannot do on the source do it at the sink if do not want to break e2e encryption. The DNS blocks have been taking down half of cloudflare in the past, so would IP blocks in many casesm How to make this technically effective so that you really need a bit of criminal energy to bypass it is however questionable. At least in Germany I can actually as a user disregard any copyright for books etc if someone in the world offers content without any effective protection or obviously illegal (also resharing like in the BitTorrent case get you into trouble). So what are the alternatives? Pushing DRM ? I would like to see a bit more constructive approach from mozilla. If you are the French and you see a problem. How would you solve it?
- DexesTTP 3y ago
  Note about the more productive approach: Mozilla published a blog post[0] back in late June about what solutions are already available and advising for the law to reinforce these existing mechanisms instead of mandating a new browser-level blocking thing that can easily be abused. [0] https://blog.mozilla.org/netpolicy/2023/06/26/france-browser-website-blocking/ https://blog.mozilla.org/netpolicy/2023/06/26/france-browser...
  - riedel 3y ago
    Thanks for linking. Ok, if fraud protection is the actual reason (I go with Mozilla): this makes no sense at all and is disporportionate. However, I think the bill is a Trojan horse in this case.

riedel 3y ago

I also do not quite get the GP comment. I see it also logical to block content on application layer from the OSI perspective. If you cannot do on the source do it at the sink if do not want to break e2e encryption. The DNS blocks have been taking down half of cloudflare in the past, so would IP blocks in many casesm How to make this technically effective so that you really need a bit of criminal energy to bypass it is however questionable. At least in Germany I can actually as a user disregard any copyright for books etc if someone in the world offers content without any effective protection or obviously illegal (also resharing like in the BitTorrent case get you into trouble). So what are the alternatives? Pushing DRM ? I would like to see a bit more constructive approach from mozilla. If you are the French and you see a problem. How would you solve it?

DexesTTP 3y ago
Note about the more productive approach: Mozilla published a blog post[0] back in late June about what solutions are already available and advising for the law to reinforce these existing mechanisms instead of mandating a new browser-level blocking thing that can easily be abused. [0] https://blog.mozilla.org/netpolicy/2023/06/26/france-browser-website-blocking/ https://blog.mozilla.org/netpolicy/2023/06/26/france-browser...
- riedel 3y ago
  Thanks for linking. Ok, if fraud protection is the actual reason (I go with Mozilla): this makes no sense at all and is disporportionate. However, I think the bill is a Trojan horse in this case.