I interviewed recently for a really interesting job.  The position is ostensibly called “Web Architect” which doesn’t tell you much until you realise that some of it is about putting web solutions together for a company and specifying the technologies used.  There’s an element of coding too, some administration, some presentation and some marketing.  All in all it struck me as perfect, and I want it.  There might be another interview soon, so we shall see how it pans out.

During the 30 or so minutes I took me to write the previous paragraph I encountered some issues.  Firstly, the latest version of Windows Live Writer comes with an interesting bug in it.  It is a late beta, so that’s pretty much expected.  However, this is one that I have never seen before with this product, and it only happens under a specific set of circumstances.  Your blog must be using the MetaWeblog API as an interface, and you must not have upgraded this version from a previous build.  When you try and detect the blog, it will take you through the entire process before throwing an exception.  I haven’t gone to the trouble of running a trace on the XML conversation, and to be honest I think this error happens in the code after the conversation is complete.  I was talking to Joe Cheng who works on the Live Writer team at Microsoft, and he said they had found the bug and would release a patch soon.  Can’t give you an exact timeframe on that though.  So, if you are thinking of installing the latest build of Live Writer (the “Wave3” betas) and use BlogEngine.Net then make sure that you upgrade rather than fresh installing. 

The second issue was that the ping services tab in BlogEngine.Net was all of a sudden empty of entries.  I don’t know why, but they had all been erased.  While trying to update them, I discovered a problem with the identity field for the table that holds the ping servers – it was setup incorrectly.  I think something happened when I copied the data from my dev to the live server a few weeks back, but because I was only posting from Live Writer I hadn’t noticed it.  At some point I have to draw up a smoke test for BlogEngine.Net that goes through testing for ALL of the functions before rolling out live.  Anyway, in addition to the table issue, I had to go and get a new list of ping servers as I noticed that a few have gone inactive.  One thing that I noticed is that Microsoft still don’t have one for their live search, though they do allow submission of a site map.  However, the transaction causes a nicely handled exception which dumps out the results to a log file.  Anyway, here is the new list of ping servers I have gathered:

http://api.moreover.com/rpc2
http://api.my.yahoo.com/rpc2
http://bblog.com/ping.php
http://blog.goo.ne.jp/xmlrpc
http://blogsearch.google.com/ping/RPC2
http://ping.bitacoras.com
http://ping.feedburner.com
http://ping.weblogalot.com/rpc.php
http://pinger.blogflux.com/rpc
http://rpc.pingomatic.com/rpc2
http://rpc.pingthesemanticweb.com/
http://rpc.technorati.com/rpc/ping
http://rpc.twingly.com/
http://rpc.weblogs.com/rpc2
http://services.newsgator.com/ngws/xmlrpcping.aspx
http://www.bloglines.com/ping


If it seems like I haven’t posted anything here in a very long time, then that’d be a fair assessment.  There’s no real excuse, just a bunch of little things have gotten in the way.  So, instead of a single theme for this post, there’s going to be a bunch of them.  The biggest news at the moment, apart from the financial crisis in the US is of course the death of Rick Wright.  If you don’t know who that is, then shame on you.  Rick Wright was the keyboardist for Pink Floyd, and responsible in a very large part for their unique sound.  He died on Tuesday after a brief fight with cancer.  There have been many things said about his untimely death around the world and the web, and I don’t feel eloquent enough to add anything new.  Suffice to say that his musical brilliance will be missed dearly.

I had to re-install Windows on my laptop last week.  Vista was getting a little slow as a result of all the crap I had installed on it. So I backed up the last of the bits and formatted it a couple of days ago.  Everything is all back up now, though I still need to install some minor apps.  I posted a few weeks ago about my search for a new password(s) and I think I have a viable solution.  There’s an open source app called KeyPass Password Safe that manages passwords, and also has a fairly comprehensive password generator built into it.  It allows me to generate very random passwords with as many characters as I like, in addition to specifying the characters that can be used.  So, I could generate one with upper and lower case letters, and then another which is the same but with added symbols or extended ANSI characters. They’d look like dkBaQ3iDwAlAKnmqV5Df, or 0h-y_PiWVaeKn3H3LTkO or even 5^Zl-uexa*\]YaD:jKFJ)"U%F.Y(7+bE$nxs<zN".  This makes it very useful for web stuff, as there are so many different combinations of what can and can’t be used on different sites.  Portability is something I’m still working though.  For now, I have the app installed on two PCs and simply synchronise the databases if I make a change.  However, there’s an option to synchronise over the web which might be a good idea.  The program will also run from a USB key, so it is portable.  Nicely enough, there source is completely open, so the trust issues inherent to software like this don’t exist should you decide to crack open the code.   Although it is a Windows program, there’s a Mac port, and if you have Mono installed it seems to mostly work on Linux.

There are a bunch of new builds of the Windows Live apps were released today into open beta testing.  I haven’t done much with them so far, but it should be noted that the latest build of Windows Live Writer doesn’t work with BlogEngine.Net.  I’ve mailed someone about it and been told that there’s a hot fix in the pipeline for BL.E users.  Very unfortunately the crash occurs when trying to detect the style of the blog, so you never actually get a chance to get in and create a post with it.  I’ll update more when my contact in Microsoft gets back to me. I had some nice screenshots to go along with this post, but of course I can’t actually use Windows Live Writer to compose in so they had to be removed.  The alternative would be to hand-resize the images and then manually upload them.  Damn this program makes blogging too damn easy.

My sister arrives here in a couple of days.  We had a friend from London over to stay last weekend too, so everything is a little chaotic at the moment.   Emma is going to be here for the beginning of the Oktoberfest, though I'm still not sure if we can get in anywhere.  We may have to take her there during the day and sit outside the tents if things keep on going as they are right now.  It seems that you have to book tickets for Oktoberfest well over a year in advence. To add a whole bunch of interestingness to the mix I have an interview tomorrow (now today) for a job that appears to be perfect.  Its a combination of web development, product management and internal marketing all rolled into one package called “Senior Web Architect”, and the more I think about it, the more I want it.  It has all of the functions I’m looking for in an “ideal” job – though of course I have no idea how the paper description would actually relate to the real job.  I guess I’ll find out tomorrow eh?


Microsoft recently released the Beta 2 version of Internet Explorer 8.  In case you had missed it, Google launched a browser beta called Chrome this week.  I’m going to take you through my first general impressions of each.  For purposes of brevity, I won’t include any other browsers in this, even though Firefox just released its version three browser and Opera continuously release new builds.

Google first then.  Chrome, as they have unimaginatively called it, is an open beta test, but the product seems to be fairly stable, and so it is worth taking a look at.  I say unimaginatively because the chrome of a program is the decoration around the window.  For example, the menus, title bar, window frames etc are all referred to as the chrome.  We had a product called Chrome Mail back in the old days of AOL 7 (I think, or maybe 8?), and that was even then a terrible name for a product.  Five years on, it is still a terrible name. Chrome continues Google’s tradition of releasing functional but minimalistic products that generally do exactly what they say on the tin.  It is very fast, and appears to load exceptionally quickly.  It is bloated, even though it doesn’t appear to be, but this is a beta so that might be allowed. 

Microsoft has just publicly released the second beta of Internet Explorer 8.  It is a vast improvement on the first beta, being able to render sites with more accuracy than before.  However, the one significant problem with IE8 is that many sites target Internet Explorer specifically to exploit flaws in previous versions.  The reason for this is that previous versions of IE (five and six for sure, seven to an extent) haven’t been particularly good at rendering HTML and CSS, and have forced web developers to build conditional work-around fixes into their code.  Lots of this code unfortunately filters out to IE8 too, which of course causes sites to render incorrectly.  This version is also very fast, and we’ll get to the speed thing in more detail in a minute.  There’s a lot of new features in this version that haven’t been seen before.  IE8 introduces a new feature called Web Slices, which basically puts a segment of an active web page on a button.  Its a neat feature, but browser specific so I don’t imagine the uptake will be all that big.

Both browsers have a new privacy mode, which erases the session data and doesn’t store cookies.  I’m dubious about these modes to be honest.  They’ve been dubbed “porn mode”, and to be honest that’s what they seem to be.  Microsoft says you’d use this mode to check email at an Internet cafe, or shop for a gift for your loved ones.

Now, there’s really nothing scientific to this test except me with a stopwatch.  With caches cleared and history erased, I opened each browser and timed how long it took to load this page.  There’s a flash movie on the page at the moment, and a couple of images.  Google Chrome clearly won, having taken 2.6 seconds to load, while IE8 took 4.4 seconds.  Both browsers are memory hogs though.  For a two tabbed session of this page and Google Reader,  Chrome took up 53,048KB and IE8 used 55,220KB.  Now, I have to say here that one thing has always pissed me off about the various speed comparisons you see between browsers : This is the Internet.  The comparisons aren’t completely fair unless you can completely control the bits in between the two machines, which typically means either controlling the Internet, or testing over an unused LAN.  I did that, and with cleared caches, the results were instantaneous.

Overall, the new browsers are pretty cool, very fast and very much beta products.  I do look forward to the final versions though.


Nice idea, but has anyone actually read the EULA they agreed to before clicking “Accept and Install”?  Let me give you a heads up on the section you need to be looking at :

11. Content licence from you

11.1 You retain copyright and any other rights that you already hold in Content that you submit, post or display on or through the Services. By submitting, posting or displaying the content, you give Google a perpetual, irrevocable, worldwide, royalty-free and non-exclusive licence to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content that you submit, post or display on or through the Services. This licence is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.

11.2 You agree that this licence includes a right for Google to make such Content available to other companies, organisations or individuals with whom Google has relationships for the provision of syndicated services and to use such Content in connection with the provision of those services.

11.3 You understand that Google, in performing the required technical steps to provide the Services to our users, may (a) transmit or distribute your Content over various public networks and in various media; and (b) make such changes to your Content as are necessary to conform and adapt that Content to the technical requirements of connecting networks, devices, services or media. You agree that this licence shall permit Google to take these actions.

11.4 You confirm and warrant to Google that you have all the rights, power and authority necessary to grant the above licence.

Now, it may be just me, but there's simply no fucking way that I will allow Google to own everything I ever post on the Internet with a browser.  So, just to be safe, Chrome doesn’t get to be my default browser yet.  It is a marvelous rendering engine though, and I’ll go over it in more detail in the next post.