Computers, Web, JavaScript, Stuff…
Anything web-related
From http://www.tommyvallier.com/2009/07/23/digg-advertising-gone-mad/ –
The ads are therefore taking up 49.35% of the viewable space. Let me repeat that: fourty-nine point three five percent. For advertisements. That’s MASSIVE.
Tommy Vallier gives a breakdown of space use on Digg’s homepage, and it’s not flattering.
The ads are therefore taking up 49.35% of the viewable space. Let me repeat that: fourty-nine point three five percent. For advertisements. That’s MASSIVE.
It gets even worse once the white-space is accounted for, with two thirds of the screen real-estate dedicated to advertising.
Bohemian Rhapsody played on old computer beeps
Bohemian Rhapsody played on old computer beeps
(found via Neil Gaiman’s blog, he found it at El Reg)
The OpenID library I'm using for Rosebleed (and other projects, both major and minor) is SimpleOpenID from PHPClasses.org.
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:
Comments/feedback always welcome.
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 “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.
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.
Yesterday, it was announced that representatives from Google, Facebook and Plaxo have joined the Dataportability.org workgroup.
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.
Over the past few days, I’ve put some work into the site:
More to come.
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.
I'm too impatient to wait for Calculator.app 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. [tag]Google Calculator[/tag] 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 [tag]Google[/tag] if you do it a lot:
