It’s a motherfuckingwebsite. It doesn’t need a valid certificate. You aren’t sending credit card data. You do not care if the CIA intercepts your data and finds out you are reading motherfuckingwebsite.com. Besides, if you’re not running encrypted DNS, everyone knows you are reading motherfuckingwebsite.
Nice rant. But my browser will still complain when a page is served over https without providing a valid certificate, whether that page is rendered in “hyperScript 2000 Professional” or html from the 90s
web devs vs just using a compiled language plus vanilla JS
web devs vs plain html
so many websites could be plain html if you cut out the bullshit
https://justfuckingusehtml.com/
Oh man, I almost forgot these exist! https://motherfuckingwebsite.com/
both giving a warning in Firefox is kinda ironic :D
What kind of warning? My local Firefox doesn’t complain.
Secure connection. Like there was no valid certificate
It’s a motherfuckingwebsite. It doesn’t need a valid certificate. You aren’t sending credit card data. You do not care if the CIA intercepts your data and finds out you are reading motherfuckingwebsite.com. Besides, if you’re not running encrypted DNS, everyone knows you are reading motherfuckingwebsite.
Nice rant. But my browser will still complain when a page is served over https without providing a valid certificate, whether that page is rendered in “hyperScript 2000 Professional” or html from the 90s