About a month ago (whoops!), I released another open source project into the wild, SaveTimer.

This was one of those “wouldn’t that be a cool idea” moments that spontaneously resulted in a modest little project. The whole thing was conceived, built and published in the space of a few hours!

Save Timer

Notify a user if they have not saved in a ‘watch directory’ for a certain interval.

Basic Description

This is a very simple application, written in C#/.NET 4.5.2, which observes a specified ‘watch directory’ on a given interval. The most recent file in the watch directory is examined to determine its last modified time. If this is older than the specified interval time, the user is shown a message reminding them to save their work. The user can suppress the messages for an indefinite period of time by right-clicking the icon in the ‘clock box’/system tray and choosing ‘Stop reminding me’.

This was written to support academic examination access arrangements, where users are intentionally only given access to a cut-down word processor such as WordPad, without spellcheck support. Unfortunately, WordPad does not autosave, so this application provides a regular reminder for the user to save. In this usage, the user is given a blank mapped drive to save in. In addition to the regular save reminders, the application also ensures that the user has saved in the correct directory to avoid data loss and ensure compliance with controlled conditions of where they must save.

SaveTimer logo (the Dashicons clock, licensed under GPLv2 or later with font exception)

At the risk of sounding immodest, one of the most enjoyable things about this project was jumping right back into the C#/.NET environnment, with which I have spent less time recently, and discovering that I still had all of the intuition of how to build the functionality I desired. Perhaps this is testament more to Visual Studio’s IntelliSense suggestions and the simplicity of the application, rather than my memory, but it nevertheless was a rewarding feeling to quickly go from zero to an app that does a specific task quite well!

I’m also pleased to say it ran in… shall we say, production… without causing any issues. If it saves one piece of work, I think it will be worth it!

SaveTimer is released under the GNU GPLv3 or later. The code is available on GitHub and you can also download a ready-to-run executable, if you have .NET 4.5.2 installed. No installer required!

Microsoft’s Hyper-V is a really cool virtualisation technology I have been having fun exploring. You cannot run a Hyper-V Server on a Windows 7 host, however, so in order to run it, I installed Windows 7 and Windows Server 2008 R2 side-by-side, and used it in the latter.

All that has changed in the era of Windows 8, however, and you can run a Hyper-V Server on the client version of Windows 8, if it is Windows 8 Pro. Hooray!

So, to cut a long story short, post-upgrade, I felt I didn’t really need my separate Windows Server 2008 R2 partition for Hyper-V, so I deleted it and expanded the Windows 8 partition to fill the space. Only to find that Windows now wouldn’t boot. Oops.

I originally installed Windows 7 first, followed by Windows Server 2008 R2, following best practice to install newer operating systems after earlier ones. What had happened now, though, was that I had just wiped out the bootloader that was sitting happily on the Windows Server 2008 R2 partition.

» Read the rest of this post…

I read this BBC News story about mistakenly issued security certificates recently, which allowed the people with those certificates to impersonate any Google websites and intercept traffic to them. It struck me as quite significant that this particular story made it to &#8216mainstream’ tech reporting.

There is a more detailed, and perhaps more accurate, commentary on this attack on Freedom to Tinker. It perhaps may not have been ‘cyber criminals’ as the BBC reported it when I first viewed the story!

Anyway, given the attention to this issue, I thought it a good opportunity to review this kind of attack against SSL/TLS — the security system upon which we all now depend. More importantly, I wanted to show Certificate Patrol, an add-on for Firefox that would allow you to notice a suspicious change to an certificate and thwart this kind of attack.

The weaknesses inherent in having too many organisations that are able to issue security certificates for any domain are becoming more clear. While this kind of attack is extremely rare, at the moment, ‘at the moment’ is a very poor security response! Hopefully, more awareness of these limitations of the internet’s authentication infrastructure can help put pressure on browser vendors, website owners and CAs to make everyone more secure.

Today’s release of Firefox 13 brings with it more imposed functionality changes to the only version of the browser that we can use, because it is is the only one kept current with security updates*.

This time, it is a brand new, Google Chrome-style ’New Tab’ page. I’m sure it is great for lots of people, but personally, I prefer a blank home page and a blank page when I open a new tab.

To restore the old behaviour, and have a blank new tab, browse to about:config. Accept the warning, then search for newtab. Do not change newtabpage.enabled.

Instead, double-click browser.newtab.url and set it to about:blank.

There, that’s how I prefer it again!

* UPDATE: A slight correction — there is a version of Firefox 10.x called Firefox ESR (Extended Support Release) that is kept up-to-date, so that is also an option!

The recent release of Firefox 7 has brought with it several changes. One of these, is that Firefox hides the ‘http://’ prefix in the URL bar by default.

For many people this is fine and probably a positive changes, but geeks like myself may wish to restore the prefix. (I found it especially annoying when I copied a URL from the bar and the text pasted did include the ‘http://’, when the text I copied did not! I don’t like that kind of inconsistency!)

To restore the prefix, browse to about:config. Accept the warning, then search for browser.urlbar.trimURLs. When you find the setting, double-click on it to toggle it to false. The changes should take effect immediately.

That’s better!

I was interested to take a look at the new publicly-available developer preview of Windows 8 that was released today. I have a few (poorly organised and still unrefined) initial thoughts.

After an initial hiccup running the developer preview in VMware, I switched over to a machine with VirtualBox and got up and running. The installation process was impressively speedy, even under the virtualised conditions, and asked few questions. A good start.

Initially, it is a little disconcerting not to have the desktop right in front of you after logging in, but I suspect that with a little retraining, the new ‘Start’ screen might prove a more convenient starting interface. The Windows Phone-style ‘tiles’ interface is genuinely innovative (praise I rarely would find myself directing at Microsoft) and seems to work in a fairly intuitive way.

I should mention at this point that my virtual machine setup and ‘traditional’ hardware combination mean that only a mouse and keyboard were available, making it impossible for me to evaluate the touch features of the OS (and making some of the ‘Metro’ apps and UI a little difficult to use). This is, of course, a limitation of my configuration, but it also raises an important point — if this new Metro UI will be the default even for computers with no touch capabilities, the whole thing needs to be smooth, optimised and not at all frustrating for this category of users too. It doesn’t feel this way yet — having to perform awkward drag gestures with a mouse isn’t a good experience at all. The viability of having a single operating system, with shared UI concepts, on very different types of computing devices is something that is yet to be proven.

These issues aside, I find myself quite impressed at how well the combination of the new ‘Metro’ apps themselves work alongside the traditional desktop. The disparity between the two types of apps was something I thought might make the system feel clunky and ‘part-baked’, but I find myself likening it to the Mission Control view in Mac OS X Lion — the Metro apps are like your Lion apps in Full-Screen Mode, and you still have access to the traditional desktop over to the left. In short, I actually think it works.

There are certainly some minor oddities at this stage — and obviously this is far from a finished, polished product. But there is promise in this hybrid-UI design that I hadn’t expected to find. I certainly need to spend a bit more than a short hour playing with the system before I’ll really understand what I think of its potential.

The biggest challenge will be how well a single operating system will work on very different types of computing devices — and indeed whether the hardware and software on the new generation of Windows tablet devices will be up to the task.

“What? I thought you updated this yesterday?”

Well, I did. 😛

Hot on the heels of yesterday’s auto-update-capable release, is DfontSplitter for Windows 0.3.1. This version includes a single fix, introducing a new method of avoiding the dreaded ‘corrupt font file’ error. For some unknown reason, sometimes Windows simply will refuse to work with the original fondu output file, but if simply DfontSplitter makes a duplicate of the file, it will happily see it as a TrueType font! It is very odd behaviour, and this fix only works in some cases, but it should reduce the incidence of ‘corrupt font files’ being output from DfontSplitter for Windows. This means users will less frequently have to go through a secondary hoop to get Windows to play nicely with DfontSplitter’s outputs.

Here are the official release notes:

New Features and Bugfixes

• Uses a new method to decrease the incidence of ‘invalid font file’ errors on Windows. More fonts should now convert correctly without requiring further intervention.

Known Issues

• Some fonts still require further conversion after DfontSplitter has created the TrueType font file. FontForge is one option for this.

As always, you can always get the latest and greatest version of DfontSplitter by downloading it from the the DfontSplitter project page.

I have just released a new version of DfontSplitter for Windows, version 0.3. The main change here is a brand new automatic update notification system. Like the Mac version, which uses the excellent Sparkle Framework, users of DfontSplitter for Windows can now keep the application up-to-date without having to manually check the website. This makes my development of the software easier, as I can release smaller feature releases more frequently, rather than large releases that must have a longer lifespan.

Unfortunately, because the automatic update feature is new, previous users of DfontSplitter 0.2 are not going to be notified automatically about this new release. 🙁

If you know any other users of DfontSplitter for Windows, please let them know this update is available so they might have the opportunity to keep up-to-date with this new feature too.

Here are the official release notes for this version:

New Features and Bugfixes

• New automatic update facility, similar to that of DfontSplitter for Mac. Users can now be notified of new releases in the future, which may include new features.

Known Issues

• Some versions of Windows report the TTF files that DfontSplitter creates as ‘corrupt’. Please see this workaround — https://peter.upfold.org.uk/blog/2009/08/23/dfontsplitter-solution-to-windows-corrupt-font-error/

As always, you can always get the latest and greatest version of DfontSplitter by downloading it from the the DfontSplitter project page.

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’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!