Internet Things

Foursquare Thursday

by
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

by
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

by
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

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

by

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

by

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

by

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.

openoffice.virginmedia.com

by
A screenshot of openoffice.virginmedia.com showing folders and files to download.

I know there’s at least one other person here who uses OpenOffice.org as their office suite and Virgin Media as their ISP, so you may be pleased to know that Virgin mirrors OpenOffice downloads at openoffice.virginmedia.com. If you’re a Virgin Media customer, then this is the fastest way of downloading it as it should require the least number of hops.

Virgin also mirror all downloads from Tucows and possibly some other sites so it may well be worth checking out before you download, especially if it’s a big download and you’re lucky enough to have Virgin’s 20 MB broadband offering, as you’ll be able to make the most of your bandwidth.

1000 reasons why IE is better than Firefox

by

It’s in French, but here’s 1000 reasons why IE is better than Firefox. Except that there’s only actually 14 reasons, so it’s 986 short. And some aren’t really reasons. In fact, it’s a pretty pointless piece of flame-bait designed to stir up the Firefox community.

In any case, here are those reasons translated into English, with the help of the Google Translator and my French A-level (feel free to correct me if I get any of these wrong):

  1. Internet Explorer is integrated with Windows XP so you can surf the internet without having to decide which browser to use.
  2. Internet Explorer is accessible for everyone.
  3. IE can display all web pages – not all of them work in Firefox.
  4. IE requires hardly any extensions, whereas Firefox has a plethora.
  5. IE does not ship with tabs, but they can be added if you wish.
  6. IE does not have an RSS reader, which is a fad. You can just visit the site every day if you need to.
  7. IE is less secure than Firefox, but patches are released regularly.
  8. IE is closely linked to Windows.
  9. IE does not pass the Acid2 test like Safari does.
  10. You need to use IE to access Windows Update – even though Microsoft released a Firefox plugin for Windows Genuine Advantage, they will never open Windows Update to Firefox.
  11. IE doesn’t crash when visiting online banking sites, Firefox does.
  12. IE7 will adopt the standards of 2006 and include innovations of Microsoft and others, such as RSS, SSL3 and better security.
  13. IE does not respect W3C standards in their entirety.
  14. IE is the ‘de-facto’ standard that developers work to.

There you go. Pretty lame reasons, in my opinion, and some of them are reasons not to use IE as far as I’m concerned.

[Via Glazblog]