Testing TLS and stuff

Just to conclude the drama before I abandon this nanoblog altogether...  I'm probably going to eventually put everything in S3 buckets and AWS makes TLS really easy. In the meantime, cloudfront.com gives free load balancing and TLS for personal or small sites. so, on hostmonster.com, I redirected my DNS to point to their DNS, as instructed by cloudfront, and Bob's your uncle!  Of course, the back end between cloudfront's load balancers and Hostmonster's site isn't encrypted, but it's not like I'm protecting Fort Knox. So all done for now!

Many searched pages later... It seems that there's no way to insert my own TLS certificate for www.electronicthought.net.  I *could* use encryption by not forcing redirects to my own domain. So encryption would work, but readers would get https:// 92cdaf584c46472d33afcf0d980f6685.blogspot.com   Sad! Disappointing! 👀 I'll have to think about what I want to do next. The only way that's obvious to me would be to host my own content on something like AWS and then just use Google's DNS services to point there.  But I'm trying hard not to become a web administrator, if at all possible.

I'm mostly curious about how hard it will be to enable TLS when visited directly via https://www.electronicthought.net Also, if you are looking for Electronic Thought, LLC, that not-quite-irrepressible-ok-largely-suppreseed app development shop, try http://www.electronicthought.com