Comments disabled

I temporary disabled the comments on this site. The last days I have received too much comment spam.

Until two weeks ago, I could control comment spam by using the MT-Blacklist plug-in.

Unfortunately this plug-in does not work on the latest version of Movable Type, so I had to remove it. MT 3.0D has the option to require commenters to sign up first before posting a comment, but I have not yet been able to get the JavaScript to work on XHTML 1.1.

Until I fix this, I simply keep a close eye on my comments, and remove any suspicious comment immediately. But the coming week I will be on a trip, and thus can’t watch my comments.

Therefore I decided to disable the comments until I am back home again. If you have any comment, just use the Feedback form.

Snails

It was that famous weekend again: the Aplec del Caragol. I won’t go into details, but after two days of eating and drinking I feel tired, dirty, and have pain in my stomach.

The first days with MT 3.0D

Four days ago I upgraded the motor of this site to Movable Type version 3.0D — the D is for Developer edition. Unlike many others who installed this version, I was fully aware that this developer edition could have some problems with plug-ins. Here are my findings of the first days playing around.

Dashboard

The first screen of the MT interface clearly shows a new item: the Movable Type News box. This box syndicates news from the Movable Type web site. Since I prefer to read my news in my feed reader, I immediately removed this box.

Another thing changed in the main screen is the direct access to some weblog features. The 2.x versions had for each weblog links to create a new entry and to enter the entries list. Now you can also access the comments list, the templates list and the weblog configuration screen. The one thing I am missing here is the upload file feature, since I assume that bloggers will more often upload an image than tinker with their templates.

Edit Entry

Also the Entry Edit screen has some —minor— modifications. It is now possible to specify the entry date & time the moment you create a new entry. In the older versions you first had to save your entry to modify the publishing time. That leaves only one feature that cannot be modified in new entries: the multiple categories.

Another change is that the edit buttons now also work in Mozilla based browsers, but only for the entry body. If you use the extended entry field, you still have to enter the HTML code yourself.

Comments

The comments list is new and handy feature to manage your comments. You can see the details and the status of the last comments, and open them from that screen. You can filter comments on e-mail, name and IP address, but unfortunately not on status. I don’t receive many comments, but I assume that more popular sites would love to see only the comments that are pending for approval.

Trackback

In my definition, trackbacks are nothing more than comments on my entries left on other sites. I would like to treat trackbacks in exactly the same way as comments, but unfortunately trackbacks do not have status information.

Plug-ins

Of the 13 plug-ins I use for this site, I removed two after upgrading. MT-Blacklist is not compatible with MT3.0, so I am removing comment spammers by hand again.

The Optional-Redirect plug-in is not necessary anymore, since the same can be achieved in MT 3.0 by no_redirect=“1”.

All other plug-ins work the same way as before.

Individual Archive template

Most of my time went into trying to adjust the individual archive template. There have been many changes to this template to incorporate the TypeKey service, but I have not yet been able to get them to work when served as XHTML 1.1 with MIME type application/xhtml+xml. The smallest problem was to validate the template as XHTML 1.1. The new code uses some names, which I changed into ids, and I had to edit lib/MT/Template/Context.pm so it won’t use valign and border anymore – look at line 1476.

A bigger problem is the JavaScript. Things like document.comments_form.email.value is easy enough changed into document.getElementById(’email’).value, but I don’t know how to fix document.write so it works both on text/html as on application/xhtml+xml.

The last problem I have with my template is that it shows the wrong comment form; the one that is normally used when TypeKey authentication is obligatory. I still have to find out what is going wrong here.

Internet radar

The radar is a handy and necessary tool in the aviation business. A long time ago, when there was not much trafic, there was no need for a radar; for the people in the control towers it was enough to have visual contact with the airplane the moment it arrived. But as trafic increased more sophisticated systems were needed. Nowadays all incoming and outgoing planes appear on the radar screens, unless they fly too low.

Exactly the same is happening on the internet. Ten years ago, it was easy enough to surf the few interesting sites on a weekly basis. But as the internet grew and more sites started to publish more material, this became a kludge. I am interested in the content of about 100 sites, which I try to read on a regulary basis. Some of these sites publish daily news, some of them are only updated once a month. Four years ago I had my bookmarks ordered by update frequency: I had a folder called ‘daily’ which contained sites I tried to visit on daily basis, etc. But as the number of sites increased, it became undoable to keep on visiting all those sites.

So I started using the internet equivalent of the radar: feed readers. Most sites publish their content in several formats. Besides the usual HTML pages, many sites also publish their news in a short format as RSS or Atom. My feed reader fetches those so-called feeds every X minutes, and notifies me when a site has been updated. This saves me a lot of time! But there are still many sites flying under the radar. Sites that do not provide feeds, sites which I still have to visit manually, many times only to find out that nothing has changed. I found out that I am visiting these sites less and less. They are about to dissapear from my screen, I simply do not have the time to keep on visiting them.

And I am not the only one. Many people read the texts of this site through a feed reader, and even more use my feeds to see whether I updated my site. So webmasters: don’t fly under the radar, but give your readers the option to use feed readers!

Dry season

Yesterday suddenly it was there: the summer! But wait, I can’t remember that we passed spring. That’s right, it is more like the season changed from the wet season into the dry season. Is our climate really changing, or is did this just happen accidentally?

Remove Movable Type News box

One of the additions to Movable Type is a news box in the main menu of the main menu. This box syndicates the latest news from the Movable Type site, and has a prominent position on the top right of the screen.

I prefer to read syndicated content through my news reader, and this news box simply irritates me. So I searched through the files and removed the responsible code. In case you want to do the same: you’ll need to edit the file tmpl/cms/list_blog.tmpl, and remove lines 7-13 (starting with <div class=“news-box”>).

Movable Type 3.0

I have upgraded to Movable Type 3.0, and am trying to fix the templates at the moment. During the next days, posting comments might give some problems, but I am working on it.

On the web a lot of people complain about the new licences, but I haven’t got any problems with it. As this site uses only three webblogs –the main site, the photo site and one for static content– and has only one author –that’s me :-D–, I fall exactly within the limits of the free licence. And if I really need more, I have no problem paying for it. Let’s face it, they made a far better CMS than I will ever be able to make myself.

The installation went without any problems, the pesky part is in the Individual Archive templates. There have been many changes, and I will have to go through my code line-by-line to see what I have to change.

To make it even more difficult, they did not escape ampersands in their code! The same thing happened in their 2.66 update, and I really expected that they’d learned something. Anyway, soon I expect version 3.01, which fixes these errors in the JavaScript.

Another problem I ran into is their use of JavaScript as: document.comments_form.email.value = getCookie(“mtcmtmail”);, which typically won’t work in documents served as application/xhtml+xml. I have to change all these lines to use the document.getElementById function.

You notice: work enough to do, so I’ll better get back into debugging mode.

[Update 2004.05.17]: They did escape ampersands, but that I was using the wrong version of their code.

PageRank

There is a law that is valid on both the internet as on every school yard: how important you are depends on who your friends are. Nowadays on the internet, your importance is expressed as PageRank. PageRank is a number between 0 and 10, calculated in a very secret way, but based on the amount of links to your site and the PageRank of the sites linking to you. If you own a site with a high PageRank (8+) you can earn a lot of money by simply putting a link to other sites on your homepage.

Knowing this, I wondered how popular I am. What is the PageRank of this site, where on the internet popularity scale am I. I looked it up, and found that I am exactly in the middle; I have a PageRank of 5/10. I am not the most popular guy on the school yard, but neither a looser without any friends.

This made me wonder what I had to do to get a 6. What kind of sites have a 6? And a 7? So I visited some sites from my bookmarks and made a short list with example sites for each PageRank:

PageRank Example site
10 Google
9 SlashDot
8 CSS Zen Garden
7 Zeldman
6 Weblog about Markup & Style
5 Brain Tags
4 Fimcap
3 Familie Naafs - Van Dijk
2 KJG Roundabout
1 Startpagina voor Jong Nederland
0 Jong Nederland Harmelen

It was quite difficult to find sites with PageRank 1 and 2. Most sites I found have a PageRank of 3 and 4. Most popular sites reside at PageRank 8. Jong Nederland Harmelen obviously did something very wrong, since Google punishes them hard for not letting the GoogleBot spider their site.