Category: Commentary

New Host Status Update

CPU load problems are gone. It’s actually kind of mysterious. Not only is my new host more generous, and gives me an easy way to monitor load, apparently it’s actually running much better too, at a level that would have been fine on the old host. Go figure.

However, it looks like I’m only squeeking by on bandwidth now. It should be OK, but there’s not much of a safety buffer. However I’d made absolutely no effort to optimize so far. If worse comes to worst I can install Jetpack again; that should reduce bandwidth massively, but I don’t really like that plug-in too much. So I’m going to try some smaller things first. As of today I’ve enabled compression and browser cache again, but on a very limited basis. HTML caching is disabled, so basically it’ll only cache images, and only for a week. I expect this will still be a significant improvement without the risk of breaking Random or anything like last time. Do let me know if you notice any issues though. Next thing I might try is “lazy load”, but I’ll wait and see if this helps enough first.

Weird Theme is Back

Sorry, still experimenting. I may have returned to my old theme a little prematurely.

As you might have guessed, this means my “overloading” issues are not entirely over. Because of that, I still need to keep a good number of posts going up for a realistic test, but since I’ll be busy with technical junk too, expect to see more “classics” (tumblr re-posts) than usual.

Easter Status Report

I guess today is a good day to start resurrecting this blog… oh boy that was forced, sorry. Anyways, as I’m sure you know, a few things need attention, Random barely works, Tag cloud is gone without a replacement, Dark mode isn’t available, etc. And although the last word from my host was that it was no longer overloading, I really don’t like how I can’t check on this myself.

At a certain point it was important to keep a normal volume of posts going up for load testing purposes, but as dig in and try to resolve the lingering issues I may once again be updating less often.

Fuck Jetpack

So this plugin was designed by morons, apparently. It caches images forever, with no way to remove or update them. Arguably this is sort of generous… but heaven forbid you ever want to change any image on your website. They claim that deleting images or purging the cache is somehow “difficult technically”, but obviously it’s not, at all. Except for the fact that they’re morons.

Anyway, it seems the only way around this is to give the file a new name. But guess what, wordpress may also have been designed by morons and doesn’t make renaming files possible.

But fortunately, someone by the name of Milan Dinić was not a moron and wrote a nice little plugin for renaming files. That was three years ago, but it still seems to work. Thank goodness.

Anyway, if you see any filenames that start with something like fuckjetpack1-, now you know why.

In other news, I’m starting to lose patience with all this (could you tell?), so I’m just gonna turn the real theme on again and hope for the best. Worst that can happen is they ban me and I have to rebuild my site on some better host. That would be a pain, but so is getting stonewalled by these guys.

April Progress Report

So the good news is my host’s tech support said my blog is now “running normally” (i.e. not overloading). The bad news is I’m still kind of in the dark about what was wrong before and what fixed it.

I guess we’re out of the danger zone, but questions remain. Like whether I can safely switch back to my old theme.  Over the next few days I’ll be trying to get things back to normal, but it’ll likely be a somewhat slow process.

Looks like I’m the April Fool today

Sorry guys, no funny jokes, I’m not in the mood. My site got suspended again. (Same overloading issue that happened last year.) I got them to turn it back on, but doubtless it will happen again before long unless I change something. The worrying part is they now say even the next level up hosting plan (first level VPS) will not be enough. It seems there might be something abnormal going on in WordPress that’s making it much more demanding on CPU than normal. But I can’t even tell because everything is so opaque from my end.

I’m not sure what’s going to happen now. I don’t think I could justify paying $100 a month or something. Maybe it won’t come to that, but I just don’t know right now. I promise Nude World Order won’t disappear completely, but unless this can be sorted out in some non-obvious way, I’m not sure the current format is viable.

If anyone on here is good at WordPress, I could really use some help.

Regular posts will probably be sparse to nonexistent while I try and deal with this. Sorry about that.

DMCA / Report Abuse