What is going on with Google’s takedown requests?

Iggle Piggle: The new boss of the Pirate Bay?

I know I promised to take a break from Microsoft blog posts, but here’s a third one in a row. Not Windows 8 this time; it's about how Microsoft has got itself in the news for the wrong reasons. It’s been spotted that Microsoft has been sending automated copyright infringement notices to Google claiming that its copyrighted material is being infringed by sites such as, err … the BBC and its well-known hotbed of online piracy, CBeebies. The BBC was unaffected as it’s on a Google whitelist, but other sites weren’t so lucky, including perfectly reputable sites such as AMC Theatres and RealClearPolitics.

First of all, embarrassing though this is for Microsoft, it’s not fair to single them out. Their only crime is getting caught. The majority of copyright enforcement comes from the big film and record labels. As I’ve previously written, wanting to protect their material is reasonable, but their record of heavy-handedness isn’t. Although Microsoft has been criticised for collusion with the record companies, on this issue of dodgy automated takedown requests, I imagine the record companies are doing the same, if not more.

Lessons from the Narwhal

There is a lot at stake with the new user interface in Windows 8. Ubuntu’s experience from 2011 gives us clues for how this might work out.

Brace yourself Microsoft. It's your turn now.

With a new Windows version coming out, 8 is of course dominating the tech blogs. I haven’t looked much myself, but I’m assuming there’s gushing praise from Microsoft fanboys and scathing remarks from the hardcore Mac and Linux fans. I really have no appetite for a string of blog posts on one product myself, but having had a look at Windows 8, there’s now one extra thing that’s grabbed my attention other than the Windows Store, and that’s the Metro Interface (it’s now called the “Modern UI” due to a copyright row, but everyone’s still calling it Metro). I promise to move on to something else next time.

This new interface has grabbed a lot of attention, and not all of it’s good. Microsoft’s incentive is to make Windows 8 more friendly to tablet users where they desperately want to compete with Apple and Android, but they risk alienating their desktop customers. I have now tried out their interface and I can confirm it’s a right pain in the bum to operate with a mouse compared to the Start menu it replaced. I can see this being good for touchscreens, but there’s no sign touchscreens are going to replace keyboard, mouse and monitor in the office. Usability is a major issue for mass consumer software, and from the sound of some commentators you’d think this was Windows suicide.

Cross-platform is the way to go

AMD will shortly be enabling Windows 8 users to run Android apps. I would advise Microsoft to welcome and support this.

Mr Ballmer, surely you won't deprive
your loyal customers of this?

Last year I wrote a blog article on “The Ghost of Vistas Past”, outlining how high important it was to Microsoft that Windows 8 is a success (along with the mistakes from Windows Vista that overshadows the reputation of all future releases). Well, we’re now approaching the release date and I’ve been looking at the pre-release version. Have to say, there have been a lot of Windows 8-bashing comments, but it’s hard to tell whether this is just the new tablet-optimised interface they’re getting used to or something more. At the moment, this could still be anything from a revolutionary ground-breaker to a Vista Mark II. But I’m going to make Microsoft a helpful suggestion regarding their controversial app store.

Firstly, an app store is a good idea. Linux distros were doing this years before there was the iPhone, when it was called “package management”. It’s good because instead of a mish-mash of programs from installation CDs or the internet, there’s a central database which takes care of all installation and updating. And as your computer keeps track of which packages installed which files, if you want to uninstall anything, you can do it properly, instead relying on unreliable uninstallation files that came with the program you don’t want. So far, so good.

Politics versus Plan B

There is no more important place to get IT projects right than central government. Unfortunately, internal politics encourages the opposite.

This is a visual metaphor, with little or no relevance to the actual article.

Who’d be a prime minister? On one day it’s all “We Love You Dave/Gordon/Tony”, then the moment you’re under 35% in the opinion polls it’s a catalogue of everything your government’s doing wrong. This year it’s been the granny tax, pastygate, the petrol non-strike, G4S and the West Coast rail franchise to name a few. All that’s missing is a good old IT shambles. After all, the last government kept us busy with the lost child benefit discs and the ill-fated NHS system. Well, for all you restless journalists itching for a story, I recommend you keep an eye on the upcoming Universal Credit benefit system.

In case you’re not following UK politics on an hourly basis, Universal credit is a plan to merge a number of key benefits such as jobseekers’ allowance and tax credits into a single system. Benefits is a controversial issue right now, but this is a software testing blog, and the issue of interest is that this is all dependent on a new IT system being developed. Now, before I go any further, I must stress I don’t know anything about how this project is going. For all I know, it could be all going swimmingly. But what if it isn’t? There doesn’t seem to be any kind of Plan B ready if the project goes behind schedule. And if this happens, it won’t be the first, because I worked on the last IT project where that happened.

Which IT project, I hear you ask? Well, please don’t be too harsh, it wasn’t my idea, they made me do it, but – I did software testing for ID cards. Yes, those ID cards. Remember them?

Where's H. G. Wells when you need him?

Is advertising really legalised lying? In cyberspace, it seems, the answer is still yes.

Bad and wrong. But is this coming to YouTube?

Okay, I’m back. Sorry about my long period of absence from this blog. Much as I enjoy a blog on software testing, actual software testing got in the way and I’ve been super-busy for the best part of two months. But this work has finally come to a close so I can now get back to this. And the thing that I’ve wanted to get off my chest for the last two months is a pet hate to many people: internet advertising. Yes, I can hear you all now going "Oh God, I hate those things".

I’ll start with an obvious defence: if we want an internet, we need ads. Some websites, such as this one, are done by people in their spare time (which can be sporadic, as this one has just shown), whilst others, such as BBC News, are funded by other means. But for many sites, somebody has to be paid to create the content, and the only source of revenue is from the website itself. Even ad-free sites can depend on adverts. This blog, for instance, has no adverts, and I want to keep it that way, but I’ll admit that Blogger would never have developed the blogging tools and hosted the blog for free without the cut Google gets from adverts on other blogs they host. There are some interesting suggestions for online micro-payments as an alternative to ads or subscriptions, but there is little interest in making this a reality. Like it or not, adverts are just as much a part of the internet as they are to ITV.

So what went wrong at Natwest?

A lot of questions need to be asked over RBS’s computer problems – but if we want to stop this happening again, we need to listen to the answers.

An easy answer. But not a useful one.

So there we have it. For anyone who questions the value of software testing, here is a prime example of what happens when you let a bug slip through. I know we’ve already moved on to another banking scandal, but in case you’ve forgotten: many Natwest customers failed to get paid owing to a botched system upgrade. This has led to all sorts of consequences, and the obvious question of how this could be allowed to happen.

Except that when people ask this question, I fear most of them have already decided on the answer, which is that RBS is a bank and therefore Big and Evil and responsible for everything bad in the world from Rabies to Satan to Geordie Shore. That answer might make people feel better but does little to stop this happening again. In practice, what went wrong is likely to have little to do with the credit crunch or banking practices and a lot to do with boring old fact that any bank – no matter how responsibly they borrow and lend – runs on a highly business-critical IT system where any fault can be disastrous.

Is superfast broadband always a good thing?

As superfast broadband gets adopted by more and more people, we must not shut out those people who cannot have this.

Are you listening to me, Network Rail? Look how quickly this image downloads on my site.

One of the perks of being a software tester is that you can take your work home with you and tell managers of other public-facing software (especially websites) what they're doing wrong. I've recently been arguing with Network Rail over the redevelopment of Birmingham New Street station. No complaints about the redevelopment itself (anyone who's actually used this station will be able to tell you why); my problem is pages like this one. Can you spot what's wrong with it? Possibly not, if you've got a fast internet link. But if you're on a slow internet connection, it takes ages to download the pictures and chews up your bandwidth – about 5MB for three images. And to illustrate just how unnecessary this is, here is the full picture you have to download in order to view a small (304px × 172px) image.¹

This is an example of lazy programming that suits the majority but excludes the minority. This is nothing new – it is been going on ever since the internet began. In the 90s there was Netscape Mail's HTML-only e-mails (absolutely and totally utterly vital so that you can write in multi-coloured Comic Sans font), instantly rendering them unreadable to people on text-based programs such as pine. Then came Internet Explorer's dominance and the web pages that didn't work in any other browsers, or worse, did work in other browsers but blocked them anyway because “it's designed for IE”. Meanwhile, we were plagued with Flash-only websites, removing perfectly decent text content away from many users with sight disabilities. What all these have in common in that all of this was completely unnecessary – it wouldn't have required any more work to make websites accessible to everyone, just a little bit of thought.