Killing AMP

I have recently removed AMP support from my photography website. If you never heard of AMP you probably don’t care much and this article doesn’t apply to you, but for what it’s worth: AMP websites are extremely stripped down versions of normal websites that do not support a lot of JavaScript (JS). Continue reading “Killing AMP”

Curbing the script kids

On my main photography site, I’m using a Redirection plugin to track 404 errors and create redirects within WordPress. I do that because my site went through some re-structuring over the years, and in order to keep search engines happy and to find and fix my own screw-ups and typos. 🙂

Most recently, I noticed a dramatic increase in errors that obviously come from scripts that are scanning sites for leftover backup archives, installation archives, database dumps, stuff like that. Normally, I have a single page of 404 error log entries in a day. That’s 100 log entries, which is quite easily manageable, even though there’s a lot of crap in there from similar vulnerability scans. Today though, I had 35 pages or 3500 log entries – not that manageable anymore…

So it was time to do something about it, and send the most obvious offenders away via .htaccess before they reach WordPress. That way, the 404 logs I see in the WordPress plugin are “clean enough” again for me to scan them for stuff that needs fixing. Continue reading “Curbing the script kids”

The mystery of the stripped HTML in WordPress

I’ve been struggling with a problem with WordPress on my main photography website for a while. The editor would strip certain HTML, fields like <input> for example. With an “administrator” user role, this shouldn’t happen! I needed this embedded form to let people subscribe to my blog posts via email (using FeedPress) – and I already had it in place, and it was working! Continue reading “The mystery of the stripped HTML in WordPress”

Own your content

OK – Dennis Cooper is perhaps a bit confused* about things but well, he’s an artist. 😀 Anyway, this is a perfect example to illustrate what I’m very passionate about: getting your own domain, your own web hosting, and putting your valuable content online in an open system, like WordPress.

Why WordPress? It’s described in this article, quote:

“Mortgaging your site to a closed-standards vendor gives them, not you, the economic power.”

So here, Google shut down Dennis Cooper’s Blogger site, and his Google account along with it apparently. Awesome! Not, of course. There’s probably a reason for this and Google is well within their rights, defined by their terms of service, to do what they did.

And that illustrates nicely why you should really, really have your own domain and web hosting, and use an open system like WordPress if you want to make your creations available to the public “on the interwebz.” It doesn’t matter whether it’s writings, drawings, photos, or whatever else. Own your content.

Needless to say, you’ll also help making the internet the diverse and open space it should be. Because walled & fenced gardens a la Facebook, Ello, Google(+/Blogger/Photos), Instagram, etc. etc. do not help with that…


*) making a Blogger site (or any place online for that matter) the only place where you store your creations, not even keeping local backups, is completely reckless. Unless you really don’t care about what you create.

Under Attack

The new year began not so pleasant: I woke up to multiple emails from Jetpack’s “Monitor” feature telling me that all of the sites in my hosting account were down (followed by the “still down” messages one hour later), and two emails from Siteground (my web hoster), the first warning me that I’m nearing the CPU limit for the hosting account, and not much later, telling me that my account was limited because of resource overage. Not funny. Continue reading “Under Attack”