As a quick heads up – my video review of Deadly Fight in Hiroshima has been blocked internationally by Toei. My written review is still up, but the video review is done. I might try re-recording the review as video only, but honestly, the video has had a pretty good life. This is the problem with trying to discuss a visual medium in another visual medium – sometimes the people who own the works want more control of the dialog around the work than the people doing the talking – which is even more of a situation if you’re working with creators from countries which don’t exactly have Fair Use protections enshrouded in law. Ah well.

Please support my Patreon: http://www.patreon.com/countzeroor
Buy me a coffee at Ko-Fi: https://ko-fi.com/countzero
Watch my Live-Streams on http://twitch.tv/countzeroor
Check out my Let’s Plays at https://www.youtube.com/@CountZeroOrPlays

Having moved hosting companies from directly going through WordPress to going through Bluehost, I’ve possibly gotten some new readers through the site getting re-indexed. So, while I have included notes at the bottom of each post on how to support the site, I haven’t elaborated any further on those methods. So, here’s a more in-depth list of ways to support me.

You may have noticed, in the past few weeks, that my site has been looking a little weird. That it’s had a few visual hiccups in terms of how it looks and is presented. (If you’re only reading everything I write on Patreon, you probably haven’t noticed). That’s because I’ve switched my web hosting from WordPress.com to Bluehost, and I feel it’s worth mentioning why.

A smaller reason why is, honestly, it’s slightly cheaper. I was paying about $300+ a year for my hosting through WordPress.com, in order to get a plan that allowed for advertising (in an attempt to finally reach my Google Adsense payment threshold). I’m paying about $250-ish a year with Bluehost, so that’s significantly less expensive.

The larger reason is that the person who runs WordPress.com, Matt Mullenweg, has been, frankly, acting like a git. He’s been harassing hosting providers and alienating plugin authors. It’s been involved enough that TechCrunch had to write an explainer article. In short, he’s he kind of git that, candidly, is causing problems for the WordPress platform as a whole – to enough of a degree where I can sincerely see WordPress forking, the way that OpenOffice forked to LibreOffice. If that happens, and the fork comes, if I’m still on WordPress.com for hosting, I can’t go either way. So, I’m off WordPress.com, and am now on Bluehost on the foreseeable future.

As a quick note – this has broken Email Subscriptions. In the interim, I’d recommend using RSS, or following my BlueSky or Mastodon accounts.