Hey @duncan climbed on board the private-by-default train: https://jdd.io/2014/08/11/ssl-everywhere/ …
You should too.
@alexindigo The process could definitely be simplified — see crap I had to go through here: https://aralbalkan.com/scribbles/setting-up-ssl-with-nginx-using-a-namecheap-essentialssl-wildcard-certificate-on-digitalocean/ … +@timbray @duncan
-
-
-
@alexindigo@aral It’s fine to share your v0.5 plaintext site with friends - when you bring in the public, privacy becomes an issue. -
@timbray No reason SSL should be any harder. Solvable UX problem that hasn’t gotten enough attention yet. +@alexindigo
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.