UPDATE 2010-06-30: At the time of writing, the Mac version of Iron is not up-to-date and is probably insecure. I have stopped using it for now. Hopefully it can be kept up-to-date and patched to a schedule close to the normal Chromium releases in the future.

Google has come a long way since its humble beginnings in 1997 and now offer a huge array of online services. One of the criticisms often aimed at the company is centred around privacy. From searches you make on the search engine, to the contents of your email if you are a Gmail user — they have the ability to build up quite a detailed picture of what you do online.

Apparently, the Google Chrome browser itself also does various things which may impact privacy. The browser creates a unique client ID which is sent to Google when you do things such as type terms into the combined address and search bar, for example, and if the browser crashes, the technical information relating to that crash is sent to Google.

If you are someone concerned by the implications of this and maybe don’t trust Google very much, you may want to give SRWare Iron a try.

Iron is a browser based on the open source Chromium project which also powers Google Chrome, but with many of the potentially unwanted features that may impact privacy disabled.

This is a great example of open source code working well — it allows you to enjoy the benefits of the Chrome browser (the speed, interface and unique tab-as-process architectre) while side-stepping things you don’t want.

Personally, I am not enormously bothered by the privacy issues and at the moment I’m pretty happy with a Safari/Firefox combination for my browsers of choice, but if you are looking for Google Chrome, without so much Google, this is worth a try.

You can download the browser from the SRWare website.

UPDATE: The Mac version can be downloaded from this forum post on the SRWare site.

I have released a new update to DfontSplitter for Mac. Here are the release notes for this version:

New Features and Bugfixes

• The Font Suitcase format is now supported. TrueType font data inside a FFIL Font Suitcase can now be extracted with DfontSplitter.

Known Issues

• Converting TTC files on Mac OS X Leopard (10.5) does sometimes run into problems, where the TTC splitting script can’t open the TTC file. The reason for this is currently unclear.
• Moving TTF files that have been extracted from a .dfont over to Windows — please see this workaround.
• Some Font Suitcase files may not contain TTF data that can be extracted.

As always, go across to the DfontSplitter project page to download the new release.

If you’re already using DfontSplitter for Mac, simply go to DfontSplitter > Check for Updates within the application to upgrade to the new release.

Over the last few years I haven’t really found myself liking the names of major new products from Apple. MacBook Air, iPhone 3GS and even the original iPhone name I didn’t like (drop the ‘i’ prefix already!)

And now we have iPad.

The name aside, though, this looks like a cool device. It feels to me to be a scaled-up iPod touch in many ways, but with software and an interface that are really capable of taking full advantage of the extra screen space and form factor. I don’t think the iPad is going to be as revolutionary as the iPhone was for the ‘smartphone’ market and I think it might take a bit of time for it really to find the right market (beyond early adopters); people need to work out how to fit it into their computing workflow. But it will force all the other companies doing tablet computers to rethink their approach.

Will I be getting one? I answered this question on the roundtable episode of The Stealth Mac podcast that I just participated in (podcast download not yet available). I’ll wait and see. I think like many people, I need to work out how it would fit into my workflow and how I’d justify my need for it. I will certainly be interested to hear how well it works for what you can do with it in a real-world setting.

I have a little project at the moment to try and reorganise my desk in my room to actually work a little better for how I use it now. Over the last few years, I have gravitated to using laptops as my primary systems (as I’m sure many other people have also done). This means that the way I organise my workspace needs really to take account of that shift in what I use most of the time.

When I was using my MacBook Pro at the desk, I really wanted to be able to lift it up so the screen was at a greater height, for ergonomic reasons. I also have access to a standalone Apple aluminium keyboard which made acquiring some sort of stand to lift up the machine and then use the standalone keyboard quite an attractive idea.

The Griffin Elevator is actually one of the most popular, go-to products for, well, elevating laptops, especially within the Mac product ecosystem. There are alternative options to the Elevator, some more specifically tailored to the MacBook Pro and the specific model I have, but I ended up going ahead and purchasing the Elevator as my solution to this problem.

I have to say I’m pretty happy with it.

The product is basically two aluminium arms (which incidentally match the MacBook Pro’s aluminium body nicely), a plastic base in which the arms slot and two bits of plastic which slot onto the end of the arms just to provide an extra protection against the machine slipping off the end. The contact surfaces on the arms grip surprisingly well — with the MacBook Pro, there is a little bit of wobble if you try to slide the machine across them, but unless you use a lot of force the machine won’t budge.

It is quite expensive for what it is, but for me it now solves the ergonomic problem by lifting up the screen to my eye height and has the advantage of providing more than adequate room for cooling.

Just a quick note to wish everyone that visits here, whether you are a good friend, or just stopping by for a tutorial or some software, a very Merry Christmas and Happy New Year.

I hope 2010 will be prosperous and productive. 🙂

I just downloaded the new Google Chrome for Mac beta. I like to clear out my cookies after each time I quit the browser, so tracking information and so on doesn’t hang around any longer than it needs to.

On Google Chrome for Mac, there is no built-in setting to force all cookies to be session cookies, but you can use this hack to achieve the same thing. After launching Chrome at least once, then quit it and run the following commands in Terminal:

rm "~/Library/Application Support/Google/Chrome/Default/Cookies"
ln -s /dev/null "~/Library/Application Support/Google/Chrome/Default/Cookies"

The first command deletes the cookies file and the second command creates a symbolic link, so that anything dropped in the cookies file goes to /dev/null (i.e. the cookies gets deleted and not stored once you quit!)

UPDATE 2010-01-29: JeanVal reports in the comments that this process works on Chrome for Linux too. The Cookies file is stored at the path ~/.config/chromium, so just adjust the commands above to fit that path.

Not too long ago I put together a screencast which aims to introduce Mac users who haven’t played with Terminal or command lines before and try and explain some of the initial concepts and to get doing a few things.

I’d love your feedback on the screencast — you can watch it either at its page on The Stealth Mac podcast website or Part 1 and Part 2 on YouTube.

I don’t like to browse the web with JavaScript and Flash and so-on automatically enabled unless I think I need it. A large percentage of ‘web annoyances’ can be avoided simply by turning off JavaScript and plugins unless you really need them. There’s also a security argument to doing this too.

In Firefox, I use NoScript to do this and it works really well. I’ve been using Safari more and more frequently in recent times, however, and I am not aware of a similar solution for the Mac’s default browser.

So I have devised a couple of AppleScripts, which were heavily inspired by and partially derived from the example on this Mac OS X Hints page. They allow me to toggle on and off JavaScript and plugins, respectively (I never have big Java switched on at any time!)

Please note that this is for Safari for Mac OS X only and is designed specifically for the new Snow Leopard Services functionality.

I have created them as Automator Services. The benefit of making them Services is that you can then assign a keyboard shortcut directly to the script and be able to simply press that keyboard shortcut to quickly invoke the script and do the toggle. It’s a lot quicker than hunting through a script menu or launching an application and doesn’t require any third-party software.

If you’d like to use these Services, download them below. Once unpacked, drop the files in ~/Library/Services, go to System Preferences > Keyboard > Keyboard Shortcuts, select Services from the list and assign your desired shortcut to the two scripts.

These scripts use Growl to notify you of the toggled state after the script has run. You’ll need Growl installed to make full use of it.

Download the Toggle JavaScript and Plugins scripts (zip archive, 270 KB)

I’m not a fan of the new ‘Ribbon’ interface that debuted in Office 2007. I have been playing around with the new beta of Office 2010, where the Ribbon is now the standard user interface across the suite.

In this short screencast rant, I explain why I just don’t like this new user interface and how I don’t think it actually solves the issue it was designed to solve.

Apologies for the poor resolution and audio quality of this screencast; in future screencasts done using this method I’ll be sure to optimise things better.

Comments here or over on YouTube are welcome. I realise many people are happy with, or even passionate about the new Ribbon for good reasons too. I just can’t see how it does any good, yet requires extensive retraining of users!

I was invited back on Matt Hillyer’s Stealth Mac Podcast on Sunday for another roundtable episode, focusing on an Apple gift guide for 2009.

Joining me and Matt were Hugo Poon and Stu Helm. It ended up being quite a marathon podcast (over two hours of recording time) and we did stray into some other topics too, but I had great fun recording it.

Because of the fairly extensive length of the podcast, it has been split up into two parts that you can listen to. Feel free to take a look at Part 1 and Part 2.

You can also subscribe to the podcast in iTunes.