Comment

sab@kbin.social ⁨9⁩ ⁨months⁩ ago

And http still works in any browser I know of.

I kind of get your frustration though. I set up my personal website precisely to get away from big platforms; yet my HTTPS is validated by Google. It feels like a defeat still having them involved in the process.

source

Sort:hotnew top

Semi-Hemi-Demigod@kbin.social ⁨9⁩ ⁨months⁩ ago
I have HTTPS on all my services and the only third-party involved is Let's Encrypt.

If I really wanted to, I could create my own authority and certificates, and as long as people connecting to it trusted my authority they'll have encrypted and trusted connections without any third party involved.

source
- sab@kbin.social ⁨9⁩ ⁨months⁩ ago
  Yeah, there's ways around it for sure, so it's not the end of the world.
  
  I'm not super technical though, so as my hosting provider uses Google for HTTPS authentication I'll just reluctantly stick with that for now. Of course I could have found a different provider, but I found it a somewhat difficult market to navigate. I'm enough of a rookie that part of me is just happy things seem to be working - when I set up the website a few months ago I kind of assumed HTTPS was some black magic stuff that I would never manage to implement.
  
  source
  - Semi-Hemi-Demigod@kbin.social ⁨9⁩ ⁨months⁩ ago
    I remember when I thought it was black magic, but after doing some work creating my own certificate authority and self-signed certificates it makes a lot more sense.
    
    Now Kubernetes, that's black magic
    
    source
Dr_Satan@lemm.ee ⁨9⁩ ⁨months⁩ ago
Thank you.

Use http and Chrome calls you insecure and there’s a red flag and you have to hit a special button… daunting for the average user for sure.

Firefox is good tho.

One person pointed out that letsencrypt is backed by a bunch of good powerful people. Which might be bullshit but it makes me think again.

source