More blogging on my blog
I’ve mentioned having moved my blog over to a new server. I’m much happier with my new host. In addition to the lowered cost of my blog (so far hosting is a few cents per day instead of the cheapy $4 per month plan at go daddy, which wasn’t too bad by itself), At my new host, I get real access logs, a prompt in my very own chroot jail, and a free statistics package. It’s a fantastic bargain, and gives me almost the type of control you would get if you had root access on your own box co-located at a datacenter. You are, however, expected to know what you are doing. If you have no clue what a robots.txt file is for or where to upload the one you wrote yourself, this is not the service for you. I’ll be doing a full review after a month or so.
Anyway, some of the unresolved problems are that some of the posts and comments got corrupted when the database was uploaded. I’ve fixed some of them by queries to the MySQL database, but sometimes it’s just easier to use the blog interface. Unfortunately that updates the date field (which updates the damn RSS feed). At least I have a great idea for a WordPress plugin now.
With the real server logs, I’ve now noticed that this MySpace bimbo seems to have hotlinked to this (watermarked) photo.
It’s too bad I’ve moved the photo archive around a bit and her hotlinking no longer works.
Also, someone in Europe is again got a hard-on to link to this photo, which isn’t even mine, I borrowed it from the AP.
If it’s the same guy, he’s made repeat attempts to view the photo, coming in from images.google.nl and images.google.be each time. I’ve added a line to my robots.txt to keep Google from indexing and storing my photo catalog. That should cut down on the hotlinking quite a bit.
I’ve be quite surprised at the amount of bot traffic. I’m wondering if they are going nuts over the new IP addresses, or perhaps this is the normal level of traffic. Search engine web spider bots don’t usually show up on the Sitemeter type logs because they rarely follow those types of links.
The last curious thing was from the bot Slurp (from Yahoo). For some reason Slurp was hitting a the subdirectory at /blog/. I did have things there for a day or so, but I never had the DNS pointed to new server during that time. I can only guess a human assumed I’ve moved my feed and hand entered the new (presumed) location. Dude, I always do proper 301 redirects.
Oh, and hi to that one person still using the WebTV browser.
