3 ms·
If you care about the Web's openness and accessibility, register your own domain, host it yourself, and write Lynx-compatible HTML. HTTP access for older brows
by forgotmypw17 6y ago
If you care about the Web's openness and accessibility, register your own domain, host it yourself, and write Lynx-compatible HTML.
HTTP access for older browsers is a nice touch. If your site works with Netscape and Mosaic, it shows you mean business.
- aboringusername 6y agoHow do you register a domain? Can I do this without using JS and Google knowing? What's that, I need to do a Captcha and use my real information so that if I post ANYTHING someone doesn't like I can be shot in the head once they find me via WHOIS which every LEA on the planet has access to? "Open", sure.
- tannhaeuser 6y agoDNS and its per-TLD registration procedures/rules and mandatory protocols for transferring your domain to another registrar (depending on the respective TLD) are about as open as it gets. Which is probably why Google et al want to kill it via DNS-over-HTTP and complex amendments to the DNS protocols themselves.
- bitwize 6y agoTraffic to and from an HTTP site can be intercepted and spoofed by third parties. Use HTTPS, always and everywhere.
- forgotmypw17 6y agoHTTPS has its own downsides, and I disagree that you should always use it. When accessibility is paramount, HTTP is still better, because the risk of MITM is overtaken by all the things that can break with HTTPS, such as: Wrong SSL version Client date is off Client doesn't have proper certs installed Server cert is broken or misconfigured SSL takes too long to set up over slow connection No one's going to MITM my blog, while using HTTPS often impairs my own ability to use it. Also, if you think HTTPS can't be intercepted and spoofed by anyone, you're kidding yourself.