Returning to a self-hosted blog is always an adventure in and of itself. That is one way to put it.
When I think back on my very first blog in 2001, the world on the interwebs was still simple: make a Blogger account, automatically host on blogspot, don’t worry about being spammed, invaded or sued. Publish posts to your heart’s content while the sun is shining down on your keyboard. Somewhere between 2010 and today, I made the decision to self-host after Google bought Blogger and gradually dismantled everything to do with the service, support and feedreader. I realize people still use Blogger for convenience but Google treated it like an ugly stepchild and that never sat well with me. I was also suspicious of the copyright situation around blogging on a hosted platform and I really wanted threaded comments. Hence my journey to export my then blog, Raging Monkeys, to a self-hosted WP blog.
I recall this being a relatively painless procedure thanks to the fact that a) many other bloggers, including WoW bloggers had done it before me and b) there were plugins to help with things like feed redirection, perma-link redirection and importing posts and comments. It’s pretty amazing to me now really, considering things have become such a headache ever since.
Security headers, blogrolls and where the hell is my feed?
Nowadays of course, nothing comes easy anymore. Self-hosting means I am running version updates for WordPress, Jetpack and many other essential plugins on an almost weekly basis. I’ve had to figure out how to buy and install my own SSL certificate for the blog because my webhost doesn’t automatically take care of that. Oh, how I love the CPanel!
Since returning to the blog this year, I’ve also noticed a new cockpit feature telling me about my overall site health. This seems wonderful but is actually every layman’s worst nightmare because half of the recommendations might as well have been written in a different language. What are security headers? Why do I need a persistent object cache? What or who is “utf8mb4” and why do they need an update? I am not prepared!
After consulting mates, browsing the WP.org forums and opening my own threads to deal with the more important risk factors, I’m now at a point where the relevant security headers seem fine at least. Or maybe not but that’s what https://securityheaders.com is telling me, anyway. I’ve also been dealing with the uncoupling of my blog’s feed from the old feedburner which has become buggy and slow. Whenever I publish new posts, they seem to take hours or days sometime to show up on feedreaders or blogrolls, so I had to reverse-engineer what I’ve done (apparently, because I don’t remember!) several years ago on feedburner. I now know where to find my .htaccess file and what to do with it, it’s a whole new world!
My blog’s feed now seems to work the way it should, that is /feed does no longer redirect to anything. It is found at “https://www.mmogypsy.com/feed” which is the standard for most blogs. I’ll have to see if that fixed all issues (feedback is appreciated!), either way it’s good to be rid of feedburner. Speaking of blogrolls, I have given up any attempt to simulate the old blogger blogroll on the sidebar. After too many frustrating attempts with different plugins, all of which seem to NOT work one way or another, I’ve had to content myself with some block-code widget. It’s not pretty, it’s not alphabetic and it won’t change order according to time published which is why I’m calling it the “Bad Blogroll”. Still, it’s essentially the information I want and a semblance of normalcy. I’ve started adding more blogs now and shall be on the lookout for more as I rediscover the gaming blogosphere!