NASA - Phoenix Images

For more on the Phoenix project, check out NASA’s mission page, or MarsPhoenix’s Twitter feed.

Slideshow at Photobucket »

Very nice set.

The original class did most of what I needed, but I made some minor changes. I’ve emailed the original contributor to offer my changes back, but until I hear back, I’ve posted my modified version here:

SimpleOpenID class

Comments/feedback always welcome.

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 “roosenmaallen.com”. This site delegates to my ClaimID page, so the openid.identity response is http://openid.claimid.com/silvermoon82, and this is what I actually use to identify the user.
To my thinking, I should be able to log in using “roosenmaallen.com” (since that delegates to my ClaimID), or claimid.com/silvermoon82, or openid.claimid.com/silvermoon82. 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 “claimid.com/silvermoon82″. I’ve gotten in the habit of logging in using roosenmaallen.com; 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 www.example.com as their Identifier, but have Consumers actually verify http://exampleuser.livejournal.com/ with the Identity Provider located at http://www.livejournal.com/openid/server.bml, they’d add the following tags to the HEAD section of the HTML document returned when fetching their Identifier URL.

<link rel=”openid.server” href=”http://www.livejournal.com/openid/server.bml”>
<link rel=”openid.delegate” href=”http://exampleuser.livejournal.com/”>

Now, when a Consumer sees that, it’ll talk to http://www.livejournal.com/openid/server.bml and ask if the End User is exampleuser.livejournal.com, never mentioning www.example.com 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.

Good luck in the Outer Planes, Gary.

Original post @ Myke’s ‘blob | digg story

On which note, this should be required viewing before a man is allowed to use a public restroom unsupervised:

This is a huge step towards an open, interoperable social web; Google and Facebook are probably the two largest collectors and holders of data (social and otherwise) on the web, and they have been among the most reticient about sharing their data.

Vintage Computing and Gaming | Archive » Why Super Nintendos Lose Their Color: Plastic Discoloration in Classic Machines

The article focuses mainly on the SNES, but mentions old Macs as well, and should apply equally to anything made of the official “this is a computer” grey or beige plastic.

The short version: Plastic is an organic compound (made of basically the same stuff as people) which breaks down over time. As it breaks down, it reacts differently to light and turns yellow. If the composition of the plastic is not perfect (exactly correct proportion of catalysts, flame retardants, pigments, &c.), the breakdown will occur faster. It’s also accelerated by visible and UV light, heat, and oxygen.

The yellowing is caused by the chemical composition of the plastic changing, so it’s irreversible. The author does go on to list some ways to mitigate the damage, but reiterates that there is no non-destructive way to fix it — you can remove the damaged plastic, or cover it.