Sun, beer, friends

We had a wonderful afternoon down at the Concordia Club, drinking German beer, eating schnitzel and pork knuckle, hanging out in the sun.  A fantastic, lazy Sunday.

In the photos are Matt's pork knuckle, an "after" shot when Louis picked up and sucked on a lemon (I wish I'd had the video camera rolling), and Jameson and Maz with pilfered flowers.  Videos are material for the documentary that will be made when Louis is a world famous footballer, and Jameson grooving to the Schlager.
Posted

Child bike seats are problematic

Louis is in daycare and Holly starts back at work two days a week on Monday, so our attention has gone to a seat on our bikes for the boy to help with the daily commute.  It's a bit problematic.

To start with, Australians get royally ripped off. The Weeride, pictured below, costs US$60 in the US.  In Australia? $170. On current exchange rates the price should be around $61.

kanga.jpg

WeeRide is a front seat, so the kid sits in front of you but behind the handlebars. That means you can chat with them, and the bike is a bit more stable than a rear seat.  When I tried a friend's WeeRide, my knees hit the seat. Not ideal, though I'm told if it's properly installed that's less a problem.

media.nl?id=6848&c=980629&h=f0c370a4c463c6edf1ea&resizeid=-1&resizeh=180&resizew=180

So we've been looking at rear seats. Problem with those is that you can't generally use panniers with them, so how do you carry all your kid and work stuff?

One seat range that might solve this problem seems to be the seats from Hamax.  They have rack-mounted rear seats and a matching pannier that will fit underneath.  Alternatively they have the "Kiss" seat, which hands from its own frame-mounted carrier and looks like it might have space for a pannier!

hamax_kiss.jpg

Anyone got any experience with these seats?  Ideas? Opinions?

Erm, thanks but no thanks

Being invited to attend a company's "Customer Advisory Board" is nice.  It recognises my real-world experience with their products, and hopefully means some of my ideas will end up in the product, making my work life easier in the future.  I'm not surprised that I've been asked to sign an agreement, since I'd be giving them ideas that might end up in their product. However I most certainly don't expect that agreement to include the following clause:

You further agree that you shall not make, via private blogs or any other communication method, negative or misleading comments about <company> or our products

If that's the way you want it, you'll have to live without my attendance.

Malt whisky ginger cake recipe

via guardian.co.uk

I made this over the weekend with some of the lovely Bruichladdich "Peat" multi vintage whisky that Louis received for his first birthday. It was amazingly light, with a very complex, adult flavour to it. Definitely one I'll be making again!

Dear Labor, please vote down gay marriage, sincerely Greens

It appears Labor will vote as a bloc against the Greens gay marriage bill. To get to the lower house it will probably require the support of the Liberals, but tactically that might be a smart move on their part.

Now if Labor do vote it down the in Reps, here's a little preview of the Greens election material at the next Federal election in those marginal lower house seats.


I know where you've been

Reading the site behind the evil evil evil evercookie hack (evil, almost indestructible cookies), I stumbled upon the author's CSS History Knocker code. This is something I'd toyed with in the past but never really came up with something I could apply it to, or a business evil enough to let me try.

The basic idea, articulated by Jeremiah Grossman back in 2006 (I can't remember where I first heard about it), is that browsers expose a piece of privacy data, the history of URLs you have visited. In the old days, links were blue and underlined. Links you had visited were purple and underlined. Along came Cascading Style Sheets and this became something designers could style, so the colours could be anything. Along came widespread and mostly-usable JavaScript, and suddenly you could get hold of that information.

The possibilities of this kind of sneakiness are pretty awesome, and scary.  Let's say you're a bank, you can know which other banks the user has visited, and present your offer with direct comparisons to the offers of other banks the user has visited. If you know the logged-in URL of a competitor, you can tell who of your visitors are your competitor's customers and make offers or inducements specifically for that audience.  Cool.

Of course you plug this kind of thing into an ad network and all kinds of evilness can start to be done.

My demo page

And so I present my edition of the CSS History Knocker.  Chrome seems to have plugged the hole, so try Firefox, Exploder or the Android browser. Haven't tried Safari.

Shred the week

Time-Killing ‘Chrono Shredder’ is a Day-Dicing Wall Calender

Wall clock, calender and mortality reminder all wrapped up in one odd work of (post)modern art. The so-called ‘Chrono Shredder’ provides a palpable (or pulp-able?) physical reminder that all things are temporary, and we can never wind back time in this world.

via dornob.com

I love wacky conceptual art like this. If the shredder were suitably quiet, I reckon I'd have one of these in my house!

Tags
Posted

Distributed social networks and security

Most of you will know I'm not on Facebook. By the time Facebook came around, I'd already been on Friendster, Orkut, LinkedIn and the rest and lost the desire to really get into a new social network. That was topped off by the fact the only people I knew on Facebook were annoying trustafarian American college kids I met while backpacking in Europe, due to the at-the-time closed-to-non-American-college-kids nature of Facebook. Then the privacy problems of the service, and the fact they claimed copyright in everything you uploaded, kicked in and I've never wanted to join that particular club.

Thinking about the independent social network efforts, like Diaspora and GNU Social, I can't help but think the problems they're trying to solve are quite insurmountable, and possibly even worse in a distributed architecture.

The big problem is information leakage: some dumb kid uploading nudie photos of himself and only intending them for a specific audience that then are made available further than he ever wanted. This problem is pretty tough to beat when you're in a distributed environment.  What's to stop someone having a malicious, or infected, client that instead of honoring the "this is only available to you" flag, instead passes the information onwards?

We all know that the average consumer Windows PC is a swirl of malware and viruses, and consumers are none too good at observing information security no matter how obvious you make the steps.  The volume of spam arriving in your inbox every day is testament to the fact someone, somewhere is being suckered in by the messages contained therein.

At least with a centralized architecture, there's at least only one single point where the security must be tight.  I really don't see a way around this in an open, distributed architecture.