[nerd]
Several days ago I switched from http:// to https://. This is supposed to keep monsters at bay. Ideally you didn’t even notice? If it’s an issue, someone tell me.
Also, I put up a privacy policy because someone said I ought to. It’s up on the header. It’s pretty much whatever the hosting software spewed out but it’s there. Something is better than nothing right? If y’all have constructive criticism, hit me in comments or with a private e-mail.
[/nerd]
Your blog comes up just fine, keep on “truckin”
Good.
No issue fr me and it shows up in my RSS feed just fine. I’ve been using a browser extension to force https connections for a long time anyway.
Excellent.
Works fine here. Now git to work on those squirrels!
Yeah!!!
Squirrels will ensue. All I need is time; real life has been kicking the shit out of me lately. I promise I’ll finish ’em as soon as I can.
Looks good, just put a redirect from 80 to 443 and you’ll be rock’n
OK, you win. I have no idea what that sentence means. I’m not a complete idiot but I have a short boredom threshold for anything networking and media related. I suspect it’s a great idea and want to learn. Shoot me some details (comment or privately) and I’ll see if my monkey brain can figure it out.
Chrome notices. Blogs that are not https:// are labelled Not Secure, sometimes in red, as in the case of the Z-man blog.
And it works just fine. Thanks.
Good to know. You’d think a blogger would spend more time sussing out the things that run under the hood but I’m a bit lazy at that stuff. Glad it’s working right and I’ve officially checked something off my 2018 “to do” list.