5 ms·

These are the symptoms. The diseases are centrally controlled IP, DNS and root certificates. The removal attempt of HTTP/1.1 is the biggest censorship in hist

• squarefoot 3y ago
  > The only way to fight back is to self host DNS, HTTP and SMTP at home. Agreed, but DNS at least needs to be shared via encrypted p2p, to avoid congesting someones broadband with million requests and prevent the inevitable hijacking by malicious actors.
  • sprash 3y ago
    > needs to be shared via encrypted p2p You mean blockchain? DNS has been solved with namecoin more than a decade ago. One of the few blockchain applications that actually make sense.
• diarrhea 3y ago
  > The removal attempt of HTTP/1.1 is the biggest censorship in history. I’d love some more context on this.
  • bullen 3y ago
    All browsers now default to blocking HTTP URLs. Anti-virus software blocks native applications that use HTTP.
    • computerfriend 3y ago
      HTTP/1.1 on TLS works perfectly fine.
      • doublerabbit 3y ago
        Your missing the point. In that browsers insist that you now -must- have HTTPS. And that if you wish to serve an static HTTP website over HTTP you can not without a glaring "This site is unsafe" thrown in your face.
        • computerfriend 3y ago
          > The removal attempt of HTTP/1.1 is the biggest censorship in history. You're missing the point, which is that this statement has nothing to do with TLS.
        • labcomputer 3y ago
          That's because it is unsafe. Without HTTPS, an attacker can inject arbitrary malicious javascript into the page. The only context in which plain HTTP is ok on today's internet is when you a loading a page from your own server on the same LAN, behind a firewall, when you are reasonably sure that nobody else is in you network.
          • doublerabbit 3y ago
            > That's because it is unsafe. Without HTTPS, an attacker can inject arbitrary malicious javascript into the page. No they can't. If they can inject malicious content then you should fix the exploits on your platform. HTTPS isn't going to save you. If exploitable under HTTP hey can do the same under HTTPS. So, How is a static webpage of "hello world" unsafe? <html> <body> hello world <a href ref="byesantiy.html"> sigh </a> </body> <html> Replace hello world with whatever information. My father stores his studies in HTML, no GETs, POST requests. Just a href to the next page. Unless you have actual access to the html file.. You tell me, why should I require cert for that following syntax? You don't.
            • precommunicator 3y ago
              Now try connecting to public wifi with that. Doing a MiTM and replacing anything with anything else is super easy. Just put a router with some Linux distro acting as extender (or mobile connection AP) with the same name and you can change traffic on any non-HTTPS website. Or not even a public wifi. Someone can put a device somewhere between your home and ISP and MiTM attack you the same way as above. Oh, and I will just show you fake e.g. Google login page, not just replace the context. And you are tired and just want to use the web... You won't notice the unsecured connection.
    • RandomWorker 3y ago
      Luckily you can get the https easily. I’ve been using https://letsencrypt.org/ https://letsencrypt.org/ to get it encrypted. Was fast and free. No real barrier just a bunch of setup.
      • edgyquant 3y ago
        How is that not a centrally controlled root certificate?