4 ms·
Okay, sure, if you don't care about the visitors to your site, don't bother with HTTPS. Personally, I don't want visitors to my site having adverts injected by
by jamespwilliams 5y ago
Okay, sure, if you don't care about the visitors to your site, don't bother with HTTPS.
Personally, I don't want visitors to my site having adverts injected by their ISPs or public wifi networks they're connected to. I don't want to needlessly expose my visitors to having malicious JS being run on their machines. I don't want a MITM to be able to change the text that a visitor receives on my website, and make the reader believe that I said something I didn't say. Especially when the fix for all of this is incredibly simple and introduces only a miniscule overhead.
https://www.troyhunt.com/heres-why-your-static-website-needs-https/ https://www.troyhunt.com/heres-why-your-static-website-needs...
- timw4mail 5y agoI don't want to require an up-to-date computing device to visit my website. I have HTTPS (with modern ciphers and protocols) for my website, but I also serve it as HTTP. I really do appreciate the advantages of HTTPS, but I have issue with the time-bombed nature of the technology: website certificates, root certificates, and ciphers that become less secure. I do not like that old devices can essentially no longer use the web due to HTTPS.