3 ms·
Which means any pure HTML resources would either have to rely on let’s encrypt or pony up some certificate money. So basically a death knell for homepages.
by jevgeni 6y ago
Which means any pure HTML resources would either have to rely on let’s encrypt or pony up some certificate money. So basically a death knell for homepages.
- dalu 6y agoespecially if the diplayed warning looks like a "ThIs Is An InSeCuRe SiTe" warning. self signed cert? WaRnInG!!!111eleven no https? WaRnInG!!!111eleven cert expired 2 hours ago? WaRnInG!!!111eleven
- jevgeni 6y agoIt amazes me that the HN crowd tear Microsoft to shreds for embrace-extend-extinguish, and then turn on their heels to cheer on crap like this without a second thought.
- ezequiel-garzon 6y agoWhy does relying on Let’s Encrypt entail the death knell for homepages? I respect the whole gatekeeping argument, but homepages will still be around.
- jevgeni 6y agoBecause relying only a single entity sponsored by corporations to protect people from corporate gatekeeping seems like a dumb idea in the long run.