Warning this article may contain opinions of the author that you and iTWire don't necessarily agree with. Don't let them get away with it - have your say with a comment!

No. 1 Story

ACCC clears Optus to scrap HFC network and use NBN instead

The ACCC has cleared, provisionally, the proposed deal between Optus and NBN Co under which Optus is to be paid around $800m to shut down its HFC network and transfer customers onto the NBN. read more

Safari 3.2.1: fix or no fix?

Opinion and Analysis

Apple has released the 3.2.1 update for the Safari web browser less than two weeks after its predecessor. What's going on?

Apple released Safari 3.2 on November 13, and followed up with version 3.2.1 on November 23.

The company merely states that Safari 3.2.1 "includes stability improvements and is recommended for all Safari users."

Exactly what's been improved remains uncertain. What we do know is that some people are still reporting the same problems that they experienced with version 3.2.

MacFixIt quotes a reader thus: "Still crashing. Safari 3.2 was crashing, I changed back a version. Tonight I went to 3.2.1 and it has crashed every two or three minutes. Going back again."

Over at MacInTouch, one reader commented that "The latest version of Safari is as unstable in my G5 running Tiger as 3.2 was", while another said "The Safari 3.2.1 update (on Tiger, 10.4.11, on a 2006 MacBook) caused Safari to be unable to launch."

One relatively common source of problems (and keep in mind that you're far more likely to hear from someone with a problem than those for whom the upgrade is working properly) with Safari 3.2 was incompatibilities with various third-party add-ons for the browser, such as PithHelmet.

Why is that a problem, and what can you do about it? See page 2.