WordPress 3.2 & new theme

If you are a regular, you may have noticed that I switched theme. I was using the excellent fusion theme that I found on this site, which like the theme seems to be no longer maintained. So when I upgraded to wordpress 3.2 this morning, I noticed there is a new default theme in there that I kind of like.

The best feature is support for multiple header photos. So I’ve cropped and uploaded a few photos from my collection and the site will now randomly pick one of the photos listed below. So simple, but so nice to have. Otherwise the theme is pretty basic, which I think is appropriate for a blog. Also it does microformats (which was a major annoyance with the old theme). Finally, it just looks nice and it is likely to be maintained for a while (with it shipping with wordpress and all).

Google Social Graph API

OK, straight to the core. I assume you got your news elsewhere.

  • Link 1:outgoing links (as expressed on my blog using xfn): link.
  • Link 2: outgoing links from outgoing links (as linked on my blog): link.
  • Link 3: incoming links (using xfn): link (thanks Christian, others use XFN already ….).

Thanks Google! So simple, so nice to have.


Normally when I play with a new browser (like a few weeks ago when I tried out Flock 1.0) I usually post at least something. In the past week I played with no less than three new browsers.

I started out by installing opera mini 4.0 on my N95. Earlier versions of this program were already quite nice and I used it a lot on my E70 before I switched to the N95. This new version adds some impressive features again. Overall quite nice but I’ll probably use the S60 browser on my N95 most of the time regardless.

The second browser I played with was Apple’s Safari 3.0.4 beta. Unlike earlier betas, this one is actually quite usable and stable. I think the UI stinks and feels really awkward on windows but aside from that it is a fine browser. My main issue with it after a few hours of browsing was that I started missing my firefox extensions and some of its behavior. Additionally the fonts it uses are different from what I’m used to and I’m not sure I like the way it renders them. It uses its own antialiasing which gives a weird smudgy look to the fonts. But to be honest, I think I could get used to using Safari full time. A nice bonus feature is that it integrates Bonjour support. This is really useful because as you may have deduced from some recent publications on my publications site, I’m working with mdns based service discovery mechanisms at work. So I installed this at work and my aptly named foobar.local N800 portal website showed up in the windows Safari browser. Cool!

Speaking of Firefox, I just switched over to 3.0 Beta1 released last night. I’ve been using it all evening and it seems a quite nice upgrade. Most of the feature work is not that important to me but the performance work is really noticeable. I’ve caught myself several times already thinking “hey this used to be slow/laggy”. It’s mostly subtle differences of course and not having most of my extensions (due to lack of 3.0 port) is great for performance probably. But still, works great and seems really stable so far.

To compensate for the loss of extensions I was able to enable the most essential ones using the nightly tester tools. This allows you to override the version check. Since in many cases, a version bumb was all that was needed, many extensions work fine. So far I have just enabled del.icio.us support. What would be really nice is a new version of that that integrates with the new places system in Firefox. Until that happens, I’m posting to del.icio.us using the old extension.

A bit of a disappointment is that none of the exciting stuff regarding ms cardspace, openid and microformats that was more or less promised a few months ago, has made it into this release. There’s no openid support, microformat features are not integrated and I have not found any UI for MS Cardspace either. It could be that this is due in later betas. There is probably still a few months until the final release.

Feature wise, most of the changes are minor tweaks and most of those were not in Alpa 7 that I tried when it was released in October?. The biggest change is the new places functionality which is nice except (as mentioned) that I use del.icio.us instead of bookmarks so this not something I will use a lot. The rest of the changes are quite nice but not that essential changes to stuff like the downloads windows, various settings screens and the url bar. For the rest it is good old Firefox, and what’s wrong with that? Next betas will introduce an updated theme. I was less than enthusiastic last time they changed it and still am rather indifferent to the 2.0 theme, so lets see what comes out.

Anyhow, unless something major crops up, I’m keeping this as my main browser.

semantic vs Semantic

Interesting post on how microformats relate to the Semantic web as envisioned by the w3c.

The capital S is semantically relevant since it distinguishes it from the lower case semantic web that microformats are all about. The difference is that the Semantic web requires technology that has been defined by the w3c but is not currently available in any mainstream products such as for example web browsers that people use to browse the current web. This technologies include RDF, the OWL query language, XHTML 1.x and 2.x and a few other rather obscure “standards” that you won’t find on a typical end user PC or web server. I use quotes around the word standard here because I don’t believe the W3C to be very effective in transferring its recommended standards over to industry in a proper way.
Continue reading “semantic vs Semantic”

OpenID & Microformats in WordPress

The good news is that Will Norris is making progress with his openid plugin. Once he puts up a release, I’m probably going to give it a try.

The bad news is that the wordpress bug database still lists as a main reason to not support openid that support is provided by third party plugins. I think this is rubbish.

First of all, they’ve broken those plugins several times with wordpress updates. Secondly, the reason they break is that authentication is rather critical to how wordpress security works (i.e. it is kind of non trivial to do properly). This is why I’d like first class support for OpenID rather than second class we currently get. And finally most of the plugins appear to be abandon-ware (they once were excellent hobby projects but people seem to have moved on with their lives) and there are no release quality openid plugins for wordpress 2.2 and higher. Will Norris seems to have adopted one of the abandoned plugins (which is very nice of him) but as discussed, I’d prefer a bit more structural solution in terms of support, testing and integration. What I’d really like is the wordpress guys getting off their ass and provide first class support for openid like the Drupal guys are doing. I hope his plugin will get some nice exposure and will eventually be picked up by the wordpress guys as something to properly integrate into wordpress.

In general, the wordpress people seem to be a bit reluctant to pick up new blog technology lately. For example, I’m using the barthelme theme which supports a number microformats and semantically structured html. Barthelme basically provides searchengines, microformat plugins and other semantic tools with a shitload of hooks to extract information from the blog. That is sort of hidden for ordinary users but kind of rapidly becoming crucial to the whole notion of web 2.0 Sorry for sounding superficial, I hate this 2.0 bullshit as much as anyone (forget about a web20 tag on this site).

Tag support in wordpress is a nice first step and it should be noted that they do it properly. Also, there seem to be patches in the bug database for hcard and hatom support. It would be great if these changes actually make it into 2.4 instead of just floating around (like they’ve been doing for some time). Also nice would be extending atom feed support to the default template. This still defaults to listing only rss feeds, despite the fact that Atom Pub has prominently featured on the last few wordpress release notes (2.2.2 and 2.3) and that backend support for Atom 1.0 feeds has been present for quite some time now. Guys: It’s just one line of text to fix! Get it in already!

xampp, skype and port 80

For some time I’ve been considering setting up some php development environment. Not that I like php but I want to play with some php stuff nevertheless (e.g. Drupal seems interesting). So I downloaded one of the popular all in one packages that combine apache, mysql and php: xampp. I have actually set up apache, mysql and php manually once on windows and know that it is A) doable and B) very tedious, hence the integrated package this time.

Xampp sure makes it really easy. Download, install, run xampp configuration tool, start mysql … green, start apache … ???!??!!! WTF, it won’t start. So I go to localhost with the browser, blank page instead of the expected error. So I check my processes list, no sign of httpd. Now this is weird, some process is definitely listening on port 80. So, I run netstat to find out who is guilty of this crime. It turns out that skype is actually listening on port 80 for some stupid reason. That just sucks. Luckily there’s an option in the skype preferences to turn it off but still, don’t open port 80 if you are not a web server.

Anyway, problem fixed and 2 minutes later I’ve created a database using phpmyadmin and installed drupal 5.2 and configured it. That’s just what I wanted: 2 minutes of work and *poof* instant website.

In case you are wondering, yes I am considering to dump wordpress. The reason is the lack of clear progress in getting proper openid, atompub and microformats support in wordpress. You can all sort of bolt it onto a wordpress install but not without editing php and default templates (and this tends to break during upgrades, i.e. every 2-3 months). Drupal seems much more feature rich and configurable than wordpress and it sure is tempting. Concerns I have include import/export of data (including e.g. uploads); openid support; comment & referral spam blocking; etc.


After playing with drupal 5.2 and a development snapshot of 6.0, I’ve decided not to migrate because simply the migration is too hard currently. There is only a seriously outdated module for drupal 4.7 which can only migrate wordpress version 2.0. In other words, this is unlikely to work for my blog without a lot of tinkering. Additionally, moving from drupal to something else is likely not exactly trivial either. I migrated from pivot to wordpress early 2006. That was quite painless since wordpress has excellent import feature. Drupal lacks such features and wordpress has no Drupal import as far as I know (would be hard due to the generic node datastructure in drupal).

BTW. I’ve spent some time researching the topic. This link here is the most informative I was able to find: http://drupal.org/node/69706. Be sure to also check the comments.

I’ve taken a brief look at joomla too. Interesting product but not really designed for Blogs. Overall, I’m pretty happy with wordpress. It’s just that I want proper openid support.

links for 2007-08-01

WordPress sandbox theme

If you are one of the handful of people not visiting this site for the first time (i.e. less than 10% of visitors), you’ll notice that for the first time since I installed wordpress, I’m not running the default theme anymore. Basically one of my reasons for installing wordpress was that despite enjoying the fiddling with html and css I got a bit tired of working around IE and mozilla incompatibilities, the many limitations of CSS and all the weird issues you run into when trying to achieve perfectly simple things like three column layouts. If you are interested in this stuff, there are several nice sites where you can read a lot of stuff about these issues.

Now, instead of getting my hands dirty, I decided to install the sandbox theme for wordpress available at plaintxt.org. This is somewhat of an experiment for me, basically my requirement is that the thing shouldn’t break down if I roll out upgrades for wordpress in the future. I simply want to keep that process as simple as possible: upload new wordpress php files and run the upgrade php script.

Basically, developing a wordpress theme means that these things become non trivial since with every update the theme needs to be tested again.

The sandbox theme has a few nice characteristics:

  • It is skinnable using ordinary CSS (i.e. like the good people at W3C have intended all web sites to be skinnable).
  • It generates particularly nice HTML. This always annoyed me in default wordpress and sort of took away my motivation to do something about making it look nicer in the browser.
  • Including nice little microformat class names for html elements where that makes a lot of sense.
  • It’s quite popular which means lots of people use it (so it is well tested) and which also means that it is likely to be updated as wordpress evolves.

Rather than develop my own CSS file for wordpress, I’ve decided to just pick one of the defaults that come with sandbox. I like the spartan skin since it is minimalistic and also tries to improve readability of the actual text. Overall it is quite nice to work with. Adding alternative sandbox css skins is particularly easy and I might actually do that since the spartan look is not quite minimalistic enough for my taste and also has a handful of issues with too small margins and paddings. On the other hand, I said the same about the wordpress theme when I migrated my blog to wordpress over a year ago (i.e. never happened). We’ll see what happens.