Schonhose

After an almost perfect record for more than a year I managed to forget uploading a photo on my photoblog not once, but twice this month. I have been so busy with other things (making photos in Snowworld (an indoor snowboard centre), designing a few websites as a favor, writing some addons) I totally forgot uploading some new photos.

Anyway, I found some room on my desk and I placed a note to remind me to a) keep making photos and b) keep uploading them. Let’s see how long this note will last in the mess I call my desk.

Back in the days when this site used my own custom written CMS I implemented a nice feature to speed up the loading times and to save bandwidth. I compressed the output using GZIP, getting on average about 60-70% compression rate. That means sending less data which boosted the loading times enormously.

Today I remembered that hack as I found out you can actually set that behavior inside a .htaccess file. So I implemented it for my Photoblog, got a nice 70% compression rate on the current page and it does load faster.

To enable GZIP compression add the following line to your .htaccess file:
php_value output_handler ob_gzhandler

You can test your page over at the gzip test tool.

Over the last few months several threads have been posted on the Pixelpost forum regarding SPAM comments. In some of these threads the author boldly claims that Pixelpost isn’t stopping any SPAM. Well, since December 28th, 2006 I have installed a SPAMlog addon on my blog. Basically, what this addon does is keeping track if and why a comment is blocked.

First I think I have to elaborate on my settings, so here they are. I use the <TOKEN> setting from Pixelpost, along with a 30 seconds SPAMflood protection setting and a maximum of three URLS in a comment. Besides that I use the http://BL addon (more info about this addon) and I have installed Defensio addon for Pixelpost.

So now we know the configuration let’s show some stats from the last 743 days shall we?

It seems my photoblog received a total of 31897 comments (43 comments per day). A total of 2457 comments actually made it through the defensive lines of both Pixelpost and the http://BL addon. Defensio managed to catch 2256 comments as SPAM, so this leaves out 201 comments. It turns out that 70 of these comments were SPAM, but these slipped through before the Defensio addon was installed (The Defensio addon was installed a few months after the initialization of the SPAMlog).

These are the numbers, but what happened to the initial 31897 – 2457 = 29440 comments which were blocked by both Pixelpost and the http://BL addon?

Let me break that number down: Pixelpost internal measures took care of 17194 of these comments while the http://BL addon took care of the other 12246 comments. Basically this says that the measures in Pixelpost are capable of catching at least 50% of all SPAM comments.

So what is the internal Pixelpost method that stops most of the SPAM?

• 887 comments contained words listed in ban or moderation list
• 10379 comments used an incorrect token
• 2 commenters waited too long before posting (30 minutes)
• 156 comments were posted to rapidly in succession (SPAM flood)
• 5403 comments contained too many URLs (3)
• 114 comments contained an URL on the blacklist
• 210 comments were not allowed (commenting disabled)
• 41 commenters used an invalid e-mail address

As can be seen the token protection is responsible for 60% of the SPAM stopped by Pixelpost own defensive measures. Feel free to comment on my analysis.

John Godley over at UrbanGiraffe.com has released the updated DrainHole plugin, which is compatible with WordPress 2.7. This means the downloads are up again! Happy leeching everyone!

At the end of November I blogged about my idea of taking 40 of the highest rated images and turning it into a book. In the post I have described a method for selecting the highest rated images but there were some flaws in my reasoning.

So I took another approach, which is much easier. Let’s assume everyone who has visited my photoblog has voted, but (and this is it) people who didn’t vote actually voted zero stars. In other words, they didn’t found the picture worth at least 1 star. When we assume this, the selection of the images becomes easier because now we only have to select the pictures with the highest total. But to narrow the selection a bit down I have included another rule: an image must have at least 5 votes to participate. Perhaps you’re wondering why I enforce this rule? The reason is quite simple. This way I know at least 5 people found the image good enough to give a rating between 1 – 5 stars.

Furthermore, whenever there is a situation in which two or more images have the same total rating the image with the least votes will be given the highest ranking.

For those of you wondering what the SQL looks like (you do need to have the AjaxRatings addon installed and I assume the prefix of the tables is “pixelpost_“) I have it included below. As can be seen I also let the statement I used earlier (weighted ratings) in the SQL for comparison:

SELECT
`pixelpost_ajaxRatings`.`img_id`, `pixelpost_ajaxRatings`.`total_value`,
`pixelpost_ajaxRatings`.`total_votes`,`pixelpost_pixelpost`.`headline`,
`pixelpost_pixelpost`.`body`, `pixelpost_pixelpost`.`image`,
((`total_rate`/5)*`total_votes`) as weighedRating
FROM `pixelpost_ajaxRatings`,`pixelpost_pixelpost`
WHERE `pixelpost_pixelpost`.`id` = `pixelpost_ajaxRatings`.`img_id`
ORDER BY `pixelpost_ajaxRatings`.`total_value` DESC, `pixelpost_ajaxRatings`.`total_votes` ASC
LIMIT 0,41


So, how does this look compared to my earlier approach? Well, the top 30 of my images stayed the same, some images shifted a bit but there were no real surprises. At the bottom of the list there were some small changes which has surprised me a bit. For instance: on number 37 (at the time of this post) was the Mosaic image I created containing the 200 images I had on my blog at that time. I’m not sure if I have a high resolution of the image lying around somewhere. In case I don’t I have chosen to omit this file.

Anyway, have a peek at the current output of the script.

At January 1st, 2009 I want to compile a list of images which have high ratings on my photoblog. The top 40 most rated images will be compiled into a real-life book.

However, compiling such a list proved to be a nice challenge based upon the information stored in the database. Currently all images have three types of statistics: Number of votes, Total rating and Averaged rating. In this case I couldn’t just sort on the Averaged rating, since images with only one vote but with a five star rating will float to the top. So basically I had to do something with the number of votes for each image.

Since the maximum rating for my blog is 5 stars I decided to divide each average rating by this maximum rating. The result is then multiplied by the number of votes. This will give a weighted rating based upon both the average rating and the number of votes.

Sorting on this results gives me a list of the top rated images which will be in a book after January 1st, 2009. Please vote for your favorite images over at my photoblog and see if your image makes it into the book.

Curious which images are currently in the book? Take a look at this crude and unstyled output of the top40 script.