A rant about BT

Communication

Earlier this week I said that our flat move had gone well and in particular that our phone line would be activated on Thursday, i.e. yesterday. It hasn’t.

Christine got a voicemail message from BT (with whom we have our phone and broadband) asking her to ring them. After being on hold for quite a while, someone finally answered, but initially didn’t know why we ringing. Eventually, we were told that there was a problem with the phone line and that the activation would have to be put back. We could have a working phone by Friday (today), but with a different telephone number, and that the broadband wouldn’t be working until Thursday next week – a week later than we’d been told originally.

To make it worse, we’re not receiving a discount on the monthly bill for the time (nearly 2 weeks) when we’ve been unable to use our phone line or broadband, so we’re effectively paying for a service that we aren’t getting.

Initially I had praise for the way BT handled our move – our first call to them assured us that it would be a quick, simple process which would allow us to keep our number. A few days without phone and internet access would be inconvenient but understandable. But having no internet for the best part of two weeks seems excessive, especially as there’s no financial compensation. And really, does it take a whole week for someone to drive over to our local exchange and press a few buttons?

The problem isn’t necessarily with BT Retail, with whom we pay the contract with, but seemingly with BT Openreach, the subsidiary of BT which owns and operates the telephone lines and exchanges in the UK. To me, they seem to be a very expensive and inefficient outfit which only serves its own shareholders, i.e. the BT Group. Although it’s regulated by Ofcom, other parties have very little say in how it’s run.

In Britain, we don’t have that many alternatives to broadband via phone lines. Virgin Media’s cable network is good, but generally limited to large towns and cities – no good for my small town. Wireless broadband over 3G mobile networks is an option: prices are coming down to be comparable with fixed-line internet, there’s no need to install anything apart from plugging in a Mifi router and they can even be bought on pay-as-you-go contracts. But wireless suffers from latency issues, making it poor for use in online gaming, and again, it’s not always available. We’re also some years away from better and faster 4G networks.

Maybe it’s high time for the ownership of Openreach to change; its shares could be split amongst the other large ISPs in the UK (Sky, Talktalk, Orange, Virgin Media etc.) so that all have a say in how its run; it could be made a not-for-dividend company answerable to Ofcom like Network Rail for the railways; or completely re-nationalised. The last one is a long-shot, but any of those should improve accountability to its direct customers (the ISPs) and regular home users.

In the meantime, I’ve paid for an extra 2 GB of data to be added on to my mobile contract with 3 for this month. Thankfully it only costs £5, and 3 don’t charge extra for internet tethering or using your phone as a personal hotspot, so I’m only partially out of pocket. I’ll still be pointing this out to BT in a letter.

In an age when I can order a book at half 4 in the afternoon, and have it on my desk at work at half 9 the following morning, how does it take so long for phone lines to be connected? Is BT’s equipment really that old and archaic, or is their lack of accountability and need to shore up profit margins the driving force here?

Enabling hardware acceleration on Firefox 4

Red Panda

A release candidate of Firefox 4 has finally been released after a very protracted beta phase (over six months), and the final release should be coming very soon. One of the major new features is hardware acceleration – using your graphics card to help to make the browser faster and more responsive – and it’s available to varying degrees for Windows XP, 7, Vista, Mac OS X and Linux users. XP users get basic DirectX 9 acceleration, Vista and 7 users get DirectX 10, and if you have Mac OS X Snow Leopard 10.6.3 or above you get to use OpenGL.

Hardware acceleration will be enabled automatically if your computer and drivers supports it, so to check whether it’s working, open a new tab and type ‘about:support’ in the address bar. Scroll right down to the bottom, and there’ll be a section called ‘Graphics’. On the very last line, you’re looking for ‘GPU Acclerated Windows’ – if it says 1/1, then you’re all set. 0/1 means that you’re not using the hardware acceleration. Thanks to Joedrew for this information.

If it is disabled, the next thing to do is to try to enable it. On a Mac, you’ll need to be running Snow Leopard and ideally version 10.6.3, so upgrade to that if you can. On Windows, you’ll probably need to update your graphics drivers. Right now, only Intel, AMD (ATI) and nVidia graphics are supported, so if your graphics card is by someone else, you’re out of luck. But for those three, once you know what type of graphics card you have, head to the manufacturer’s web site and download the latest drivers. In most cases, your drivers will need to be quite new – ATI and nVidia issued updates in June 2010 which are required for hardware acceleration to be enabled.

How good is hardware acceleration? On my test machine, which runs Windows XP and has Intel integrated graphics, I tried Microsoft’s flying images demo in Firefox 4 beta 12 and Internet Explorer 8. Firefox managed a steady 60 frames per second with no problems, whilst IE8 struggled to make 6 frames per second. IE8 also needed 50% CPU usage for just 1 tab, whilst Firefox needed 45% with 9 other tabs open.

There’s some more information on the Mozilla Wiki, including the specific driver versions supported. If you haven’t updated your graphics drivers in a while, now may be a good time to do so, so that you can make full use of Firefox 4’s extra oomph when it’s finally released later this year.

2-Factor authentication on Google

Water wheel

Google has recently enabled two-factor authentication for all users with a Google Account. This means that, when you log in, you provide two pieces of secret information, rather than just a password (which would be ‘one-factor’ authentication). This second piece is a 6-digit code that is generated randomly every 30 seconds from another device.

This improves security by ensuring that, even when a third party knows your password, they still cannot log into your account without the 6-digit code (although see below). Think of it like a PIN number – a thief could steal your credit card but wouldn’t be able to get money out of an ATM without knowing the PIN number.

Some banks have started using two-factor authentication for their online banking services – as well as your username and password, you are asked to enter a code generated by a small electronic device on your keyring. Blizzard Entertainment offers a similar device for World of Warcraft and Starcraft II players, as well as a free iPhone app that does the same thing.

So Google isn’t the first to offer this – it’s actually reasonably well tried and tested. To activate it, log into your account and click the ‘Using 2-step verification’ link. Google will then walk you through setting up your account for two-factor authentication.

There are a variety of options for the second factor. There are apps for the iPhone and Android phones, but you can also receive a code by text message to a mobile phone number that you provide during the initial setup. You’ll also be asked to provide a backup system in case you lose your phone; in my case, Google will phone my work number and a computer will read a number to me.

I mentioned there’s a caveat. Two-factor authentication works great on Google’s various web sites, but falls down if you access Google services through other apps, such as IMAP for Gmail, or CalDAV for Google Calendar, which aren’t really designed with two-factor authentication in mind. As soon as you enable two-factor authentication, any attempts to access data over these protocols will see your login fail.

Thankfully, there’s a way around it, in the form of application-specific passwords. Essentially, for each method of connecting to your Google Account, you can create a separate password. Each password can then be revoked if you find someone using it without your permission, and once generated, passwords cannot be viewed again. Furthermore, the passwords can’t be used to get into your account on the Google web site (they would need your main password and verification code), so it wouldn’t be possible for a hacker to change your main password, or deactivate the two-factor system. It’s not a perfect solution, though.

I’ve turned on two-factor authentication because I have a lot of important personal data in my Google Account – all my contacts, my calendars and hosting details for this site – and wouldn’t want anyone obtaining unauthorised access. The workarounds for CalDAV and IMAP are a bit of a pain, but I feel it’s worth it for the piece of mind.

Whilst we’re on the subject of Google Account security, if you use Firefox I’d recommend installing the HTTPS Everywhere addon, which forces the use of SSL/TLS on most parts of Google. I would, however, suggest disabling the ‘Google APIs’ option in its preferences as this may break some other web sites. Still, it will help to prevent your Google Account data being caught be man-in-the-middle attacks.

Foursquare Thursday

Barton Square

Seeing how I haven’t posted for a while, I’m going to try to post something about Foursquare each week on a Thursday as a way of encouraging me to actually write something. This week’s post is going to be an introductory one, about why I participate in Foursquare and what I feel sets it apart from its rivals.

I started using Foursquare almost as soon as I bought my iPhone, and, predictably, my first check-in was where I work. In fact, most of my check-ins are either work, or one of the two stations I pass through on my commute, due to the fact that I work full-time five days a week. But some more interesting ones appear at weekends or special events.

Obviously I wouldn’t bother participating in Foursquare if there was no reward for it. I’ve managed to get 17 mayorships (it was 18 earlier this week but I’ve been ousted from a local pub), and 15 badges, which isn’t bad but could be better. It’s certainly fun to get badges and compare with friends.

As yet, I haven’t unlocked any special deals (apart from the Super Bowl one at the weekend, which I didn’t take up as I don’t really have any interest in American Football); unfortunately there aren’t many UK companies taking advantage of Foursquare in that way as yet. Locally, there’s only Wetherspoons and Dominos Pizza. Hopefully that will improve; right now I’m the mayor of a couple of sandwich shops and some tangible rewards would be nice.

My participation in Foursquare goes beyond being a simple player, however: I’ve also been helping to find duplicate or incorrect venues and get them fixed or merged. I’ll mention more about this next week.
Foursquare for me is fun, although a bit limited as only a few of my friends also play it. Plus, the US-orientated nature of most of the brands mean that some of the rewards are out of my reach, which is a shame. Still, I enjoy it.

Not dead yet

Pagoda

I mentioned a few weeks back about several services that had been popular in the past but were now shutting down: Vox, BlogRolling, Xmarks and Bloglines.

Unfortunately, Vox and BlogRolling both bit the dust at the end of September and October respectively. But the future is much brighter for the other two.

Xmarks has a new owner and will be launching a premium service in addition to the current free service, so it’ll be around for some time. I don’t currently use it, but seeing as I can only run Safari on my iPhone (and the Firefox Home app is a little clunky) having my Firefox bookmarks available in all browsers could be beneficial, so I may sign up.

And Bloglines has had a stay of execution. Presently it’s run by Ask.com, part of the IAC group; IAC will still own it but it will be moved to another part of the business. Either way, it’s probably a big relief to those still using the service and who may have been apprehensive about moving to an alternative like Google Reader.

Finally, yes I know the picture at the top has nothing to do with this article but it’s a nice recent picture of Bradford, in the new and underutilised Urban Garden.

Demise of Web 1.5

Broken Glass

This month is turning out to be what Anil Dash calls the end of ‘Web 1.5′ – services which started before the ‘Web 2.0′ bandwagon started rolling, have not been popular for some time and are now closing.

I’ve already mentioned Bloglines, and to add to that there’s BlogRolling, which is “probably shutting […] down soon”. BlogRolling is another service that I used to use but haven’t for many years; it let you keep a list of blogs that you read (a ‘blogroll’) and allowed you to sort and categorise them easily. It made sense in the early days when people were using services like Blogger, but packages such as WordPress make this dead easy now. Its one stand-out feature was being able to show which blogs had recently updated, but this was before RSS/Atom feeds really took off and once I had switched to a feed reader I didn’t see the point of staying with the service.

Xmarks, which allows you to synchronise your bookmarks/favourites between multiple browsers on different machines, is also due to stop operating in around 9 months time. The blog post explains why in full, but essentially they were unable to build a viable business around a free service, and there’s increased competition now that Google Chrome has sync built-in, as will Firefox in its next major update (it’s already available as an add-on).

I’ve also already mentioned Vox, Six Apart’s community blogging service which also closes at the end of this month.

It’s perhaps a shame that these services are going under. Bloglines, BlogRolling and Vox have all stagnated for some time and it’s therefore no surprise that they’ll soon no longer be around. As for Xmarks, it’s a pity that they didn’t offer a ‘freemium’ service, or switch to a paid-for model; while the new sync services in Firefox and Chrome are good, Xmarks was one of the few ways of syncing bookmarks between different browsers.

I’m wondering who will close next.

Update: MSN/Windows Live Spaces is closing and its users are being moved to wordpress.com.

Bloglines closing down

Bloglines is down!

Bloglines, a web site which allows you to subscribe to and read RSS/Atom feeds online, is closing on October 1st.

It’s a bit of a shame – I started using Bloglines almost exactly 6 years ago, and it was great to be able to read all of my feeds on one central web site. That being said, a couple of year later I moved to Google Reader and have stuck with it ever since, due to its better user experience. Bloglines never seemed to catch up and I only know a few people still using it now.

Even so, the number of people using feed readers is apparently falling, and according to paidContent Google Reader is also experiencing a fall in traffic. Whether this is because of feed features in desktop browsers like Firefox and later versions of Internet Explorer have become people’s preferred way of using feeds, or that people prefer Facebook or Twitter, I’m not sure, but it would seem that their popularity is waning.

Up and running again!

At last, the move to the new host is complete!

I’m now hosting with Bytemark, a well-known hosting company based in York with data centres in Manchester and London. The domain is managed by 123-Reg – I’ve decided to keep the domain and hosting separate to make any future host changes easier.

The hosting package is quite different to the package I had previously. Whereas before I had a simple virtual host setup with FTP, email and databases, this package offers SSH access to a complete virtual machine running Debian. In other words, I can configure everything on the server essentially as I wish – even changing to a different Linux distro if I wanted to.

I’ll be sticking with Debian for now. It brings with it Apache 2.2 and MySQL 5, and I have the ability to add things like FastCGI should I wish to at a later date. I’ve also been able to install every optional Perl module that Movable Type can use, including ones like Image::Magick and XML::Parser which require compiled code.
I’m still using Movable Type 4.3x for now – it’s still supported, with version 4.34 having come out a few days ago, and having tried MT5 for a bit I think it’s a bit overkill for what I need it for.

The move to the new host wasn’t quite as smooth as I’d hoped – some issues with having the domain released from the old host, for example, and the new machine that the site runs on had a disk failure last night, literally about 30 minutes after I updated the DNS to point to the new server. It’s also taken some time to get used to configuring the server myself, rather than having a fancy-pants admin interface to do it for me. Suffice to say I’ve learnt a lot about the Unix command line over the past couple of weeks.

Hopefully now everything will work, but give me a heads-up if it doesn’t!

New host

I have just ordered a new hosting package with a different hosting company. The package offers faster and more up-to-date servers for around £5 extra per month.

The switch will take place shortly, and will allow me to upgrade to the new Movable Type 5.01 which has just been released. MT5 requires MySQL 5.0 (released several years ago) yet my current host is still offering MySQL 4.1, as well as a very old version of Apache. There’s also no support for persistent environments such as FastCGI which are key for getting the best performance out of Movable Type.

I’m aiming to have the migration to the new host complete by the 14th, which will be the 8th anniversary of the first post to this blog.

Firefox, Performance, and You

I’ve been blogging quite a bit about the beta versions of Firefox 3, which can be downloaded here, and how much better it is than Firefox 2. If anything, I’m as excited about this version as I was when version 1 came out, as it feels like the browser I have been using for 5 years has now grown up and many of the issues it has had in the past have been ironed out.

In this entry, I am going to go through the various changes that have been made in Firefox which improve the performance of the browser – the startup times, the time it takes to render web pages, and the general responsiveness of the program. Improving performance has been a major focus of the Firefox developers for this release, and the changes are notable.

Memory usage

Do a search for ‘firefox bloated‘ and you’ll get over 500 000 results, many of which complaining that Firefox is big and slow. Many put this down to the amount of memory it uses, which, in Firefox 2, appears to be more than its main competitors – Opera, Internet Explorer and Safari. (Note that, unless you’re using Windows Vista, it is difficult to measure memory usage of individual programs on Windows successfully)

For Firefox 3, reduces Firefox’s ‘memory footprint’ (the amount of memory it needs to run) was one of the main priorities. Improvements have been made both in reducing ‘memory leaks‘ – memory taken by Firefox that isn’t released back to the operating system when it is no longer needed – and memory fragmentation, which means that the memory it does have allocated is used more efficiently. The culmination of this is that, on Windows, Firefox 3 uses less memory while running than any other current web browser. It also released more memory back to the operating system after a period of inactivity, meaning that it’s no longer needed to close and restart the browser because it’s eaten half of your RAM.

How does this improve performance? If you have 16 GB of RAM, then, not much really. But if like most computers your machine has just enough RAM to perform, then it means more of Firefox can fit into RAM and less of it has to use ‘virtual memory’ – essentially a big file on your hard disk which acts as an overflow when all of your RAM is used up, but that is much slower than RAM. It will also allow more space for other programs in RAM, so you’ll be able to run more programs at the same time as your web browser.

Code optimisation

Several parts of Firefox have been re-written to fix bugs and simplify code, and in some cases, improve performance. There have been performance improvements in:

  • Page rendering – a marked performance increase that also means that Firefox 3 will pass the Acid2 test
  • Image drawing – a bug fix sorted out problems with image caching and a new JPEG decoding routine also means that images will render faster

Mac-specific improvements

Firefox 3 finally moves away from the really old QuickDraw API to the newer Cocoa API. As well as giving nicer widgets (scrollbars, buttons etc) on web pages, this also means the whole program should feel more snappy. This, combined with the new theme, means that Firefox 3 is the most Mac-friendly version to date.

Profile guided optimisation

Firefox is now, essentially, compiled twice – the first compile runs as usual, and then the compiler runs a series of tests which optimises the code by looking at what parts of the browser will be most used in a working environment. This has lead to performance improvements of at least 10%.

Because we’re now approaching the ‘release candidate’ stage, ahead of a final release probably some time in June, most of the performance changes have now been made, so if you want to see if it is an improvement for you, now is as good a time as any to try; any further changes will be to fix any major bugs and stability issues. All in all, the massive strides made in performance make Firefox a much bigger competitor in the web browser arena and may win back some of its earlier detractors.