OpenID on

I’ve finally finished up the OpenID signup for Rosebleed. The workflow is what you’d expect – OpenID box on the login form, if the given URL isn’t recognized then it redirects to the signup form and prepopulates it with the sreg fields.

I did notice a strange behaviour in OpenID; I’m not yet certain if I missed it in the spec or if it’s left to one’s judgement (note to self: read the spec again)… Anyway, here’s what happens:

– Say I sign up with “”. This site delegates to my ClaimID page, so the openid.identity response is, and this is what I actually use to identify the user.
To my thinking, I should be able to log in using “” (since that delegates to my ClaimID), or, or These URLs all end up at the same identity, so they should be equivalent — and that’s how I implemented it on Rosebleed.

I’ve noticed other OpenID-enabled sites handle this differently. On the OpenID Directory for instance, I first signed up as “”. I’ve gotten in the habit of logging in using; but when I try that at OpenID Directory, I get an error message that my email address is already registered to my ClaimID URL.

So, barring finding that the spec keeps “equivalent” OpenID URLs separate, I think I’m in the right here; always open to feedback though.

Update [2008-03-19]: I’ve checked the spec, and as it turns out, I’m actually in the wrong:

So, to use as their Identifier, but have Consumers actually verify with the Identity Provider located at, they’d add the following tags to the HEAD section of the HTML document returned when fetching their Identifier URL.

Now, when a Consumer sees that, it’ll talk to and ask if the End User is, never mentioning anywhere on the wire.

The main advantage of this is that an End User can keep their Identifier over many years, even as services come and go; they’ll just keep changing who they delegate to.

Go green by going black? …not convinced.

I just came across an interesting post about energy savings based on the colour of a webpage (specifically, Google – but the idea applies everywhere): A black Google start screen? | Wired Gecko.

I’ve found other posts dating back to May of this year (The Numbers Guy) on the subject, so it’s really not a new idea.

The largest part of my doubt is the question of technology. In a CRT, it does indeed use more energy to display bright colours than dark (ref. DOE Energy Star Desktop Information). A CRT produces bright colours by directing an energy beam at the front of the screen; more brightness == more energy used.

Continue reading “Go green by going black? …not convinced.”

I annoyed Google! Go me!

I’m too impatient to wait for to load, or for the Calculator dashboard widget to catch up with me. The solution? Google.

If my computer is turned on, there’s generally a web browser open. Google Calculator meets my needs, and it’s faster than opening a local app or taking my boots off (if I need to count past 10).The downside? Apparently it annoys Google if you do it a lot:

I annoyed Google! Go me!

Technorati Tags: ,

Pink for October

In support of breast cancer awareness and research, I’ve turned this site pink.


Web sites will Go Pink during the month of October to bring attention to Breast Cancer Awareness Month, get people talking about breast cancer, and raise money for research.

But to be clear, raising money isn’t the primary purpose of this web event.
The hope is that you turn your site pink (in whatever way works for your site), go out to that World Wide Web thing and educate yourself about the multiple issues related to Breast Cancer, then take that newfound knowledge and tell someone else what you’ve learned.

Iomega Parallel Zip Drive in Linux


This note describes how to configure the parallel port ZIP drive on a Linux system.

Older parallel port ZIP drives used the ppa kernel module, but more recent versions of the drive (After April 1998) use imm. There are slight differences between using the two modules, which will be noted as they come up.

This was written for Slackware 10.0 and kernel 2.4.26. This should apply to other distros using 2.4.x kernels, but has not been tested on kernel 2.6.x.


For a newer ZIP drive, simply run modprobe imm as root. Done!

For the older models, you’ll first need to add a couple lines to /etc/modules.conf:

alias parport_lowlevel parport_pc

alias scsi_hostadapter ppa

Then load the module by running modprobe ppa as root.


Once the module is installed, ZIP discs can be mounted as standard SCSI devices.

As well as the standard mount/umount/eject commands, Iomega offers a toolset for working with ZIP discs in Linux. This set provides mount/unmount commands, as well as password protection and formatting tools. The set is available from Iomega’s website.

About is owned and operated by me, Eddie Roosenmaallen.

My aim is to gather the collective knowledge of humanity; failing that, I’d like to maintain an interesting sort of site about the things that interest me – technology [the web, social networking, microformats, DHTML, and a bunch of other buzzwords], philosophy [spirituality, the Meaning of Life, stuff like that].