Carbon pricing and petrol

Australia is in the midst of deciding how its eventual carbon taxation and trading environment will work, and the conservatives have switched back to their default climate change denial position, as they had before they thought it might win them last year's election. These supposed fans of the free market are now calling for petrol to be excluded from any eventual carbon pricing mechanism.

Crikey has been banging on about the fact that excluding any sector of the economy from the carbon taxation means the cost of carbon for every other sector will be higher. Our government would do well to resist these regressive moves, and aim for a flat carbon price that is based solely around the carbon emitted. We are, after all, trying to get the economy to be less carbon-intensive, so any moved by any sector to reduce their carbon emissions should be encouraged, via a price signal.

Last week China removed some subsidies on processed oil products, which caused a sharp rise in prices. This change was partially caused by pressure from economists to remove the subsidies and instead focus the subsidy on those in most need of financial help. This is the same approach Australia should take.

So the eventual approach we need to take is to tax all carbon sources equally, and help households that meet the criteria of fuel poverty through direct, means-tested and targetted subsidy. Otherwise you'll end up continuing to subsidise road transport over other forms of transport, the rich will end up with cheaper fuel, the poor will still be struggling.

Obviously part of the package needs to be providing alternatives to single-occupant petrol-based transport throughout the economy.

Sniff browser history

Niall Kennedy has a really clever JavaScript hack to sniff a user's browser history. It's a pretty cool hack, but also a little scary since any web page you load can find out what pages you've been to.

It works like this: you have some links somewhere inside the DOM, and inspecting the CSS "visited" attribute, you can find out if the user's history contains the URL you're linking. Of course it doesn't actually have to be visible to the user.

His nice white-hat example presents only appropriate "add to your <social app>" links to readers. I can think of some less nice examples. You're selling stuff and want to know if the person is a customer of your competitor. Check to see if they've visited the logged-in area of the competitor's site, then present a specific comparison between your competitor and your own products. Or you could be very reactive to stuff being written about you in the press in the press, even though the person read the article a few days ago. Cool!

I'm looking at personalisation at the moment as a way to try and mediate around the inevitable conflict of home page real estate between divisions in the company. The more we can work out about people hitting our site, the more accurate we can be. This gives the evil genius in me some ideas! Mwahahahaha!!!

Liam Colm Askins

Kaz, Liam, Ben, Chris

On Friday afternoon, Liam Colm Askins came into the world a bit early. The birth was straightforward and both mother and baby are doing well. Being a bit early, Liam will have to spend a few weeks in the hospital, but he's doing well and is otherwise fine. Congratulations Ben and Karen!

Update: I spelt it wrong. It's Liam Colm Askins.

Tags
Posted

Big brother IS watching

I've been toying with an amazing new web analytics tool called ClickTale. It tracks everything a user does as they interact with your site, so as well as the usual heat maps and the like, you can actually observe a user's mouse moving around, clicks, typing, the lot! Amazing, but somewhat scary. Certainly could give some insights into how your users interact with your site, particularly complex elements like forms.

Here's a video of me testing it out to demonstrate quite how detailed it is. Wow!

Or view it on YouTube.

Google Developer Day

I went to Google Developer Day today and learnt a lot. There's some very clever people doing some very clever stuff.

The sessions I went to in the morning were iGoogle gadgets, which is some very interesting stuff. We're thinking about using some of this kind of stuff for usage indicators and the like. it's remarkably easy to knock up a cool little gadget. Next was the YouTube where I mostly read my emails, as I'm not that fussed.

OpenSocial is very interesting. The open approach definitely appeals -- I was using Friendster, Orkut and the like long before anyone discovered Facebook, and got pretty over the idea pretty quickly. I'm quite interested in the possibilities of some social networking apps, done right. Last.fm is brilliant, and gives me information about music I really care about. LinkedIn is very good for professional contacts, and does that one task well. So the open API really appeals so you could integrate all your social networking stuff. But from the sessions I went to, the OpenSocial stuff Google has is alpha quality at best right now. I'm sure it'll improve quite quickly though.

Mapplets was very interesting. It's much like the Maps API but designed to let the user put your data in as a layer amongst many, which has many possibilities. The presenter seemed very nervous talking in front of the crowd, but he actually did a really good job of explaining it, so hopefully he'll get over the nerves and become an excellent presenter.

One of the items in the morning keynote was GWT, which is a toolkit that allows developers to write Java code that compiles into optimized JavaScript. The integration he was demonstrating with Eclipse was amazing. Almost makes me want to learn the acronym-soup that is Java. But not quite enough.

It was a great day, with as you'd expect from Google excellent catering. Pretty amazing the stuff they turn on for developers, but then I guess they get the opportunity to poach the best and brightest. My only complaint would be the ditchwater coffee. It left a bad taste in my mouth all day! Ugh. It was like the worst business hotel or Amercian diner percolator shite. Maybe I'm just picky?

Heat, and keeping it in

Our
heater

We finally got our gas point installed last Thursday so we've now got our excellent gas heater. It's the Paloma PG-711FRN which is the one that scored best in the Choice comparison of unflued gas heaters. So far so good -- our house is toast warm.

Weather strip on our front door

To help keep the heat in, I've been weather stripping around the house. All the windows now have a weather strip to stop draughts. This afternoon I attached a strip to the front door. It flaps down when you close the door to block any draughts, and will also keep dust and crap out of our hallway.

Raised garden bed

Last weekend I built and planted out this raised garden bed. It's a bunch of railway sleepers with some very long bolts holding it together. Planted out are broad beans, kale, silverbeet, parsnips, chives, sprouting broccoli and four types of garlic. Yum!

Firebug site down?

The other day I moaned about Firebug crashing my browser. Seems that the reason, though this is weird but probably due to boneheaded network configuration, is that the firebug domain servers are down. Fortunately, SMS had the source on his laptop and built up an xpi for me. Sweet!

In other news, I can overhear our departmental admin person berating someone in the IT department. I requested a work laptop with at least two gigs of RAM and a "large" hard drive, as I run lots of virtual machines for browser testing. I got a gig of RAM and a 12 gig hard drive. Do they even make 12 gig hard drives any more? Mobile phones come with more than that these days!