Upgrade to Firefox 3.6 Stable in Ubuntu
28th Feb 10
This is a quick guide on how to upgrade Firefox in Ubuntu 9.10 (Karmic Koala). It’s a pretty straightforward process and only requires basic Ubuntu skills.
Start by going to System > Administration > Software Sources.
Click the “Other Software” tab, and click the “Add” button near the bottom-left. A dialog box will pop up. Copy and paste this text into the box: “ppa:mozillateam/firefox-stable/ubuntu”.
Click “Add Source” when you’re done. Click the “Close” button on the “Software Sources” screen. Ubuntu will ask you if you want to reload the list of available software, click “Reload”.
Once Ubuntu has reloaded the available software, go to System > Administration >Update Manager. New Firefox updates will be available. Click “Install Updates”.
Wait for the update process to finish, and that’s it! You’re now running the latest and greatest Firefox 3.6.
I’d imagine you’ll be able to follow these same (or very similar) steps on Ubuntu 10.04 Lucid Lynx when Firefox 3.7 (or later) is released.
You can check out the Firefox 3.6 Release Notes here.
Thoughts on Apple’s Tablet
27th Jan 10
All the Apple Tablet rumours have me intrigued. I know we’re talking about a product whose existence hasn’t even been confirmed or denied by Apple yet… but regardless, if these rumours were true, what would it mean for the masses? Should we have our pockets primed and our tents ready for the massive wait in the queues to buy “the next big thing”? Maybe.
From what I can tell the Tablet will offer multi-touch support much like iPhone & iPod Touch, and have a screen size somewhere in the range of 7 to 13 inch (anything greater or smaller would seem impractical). Assuming this is correct, the Tablet would be competing with the Netbook form factor. Netbooks have exploded in popularity because of the aggressive price points and their small, easily portable size (1.5Kg or less). They’re the perfect companion PC for light tasks such as browsing the web, receiving emails, and creating word docs on the go, all without the pain of lugging around heavy laptops. They don’t replace the need for a desktop/laptop, or Smartphone, but rather they happily co-exist along-side them. I’d imagine Apple’s Tablet to be much the same, one of those complimentary devices.
I can’t see Apple cannibalising their Macbook and iMac sales with an inexpensive tablet that does everything a Macbook does. It’s no secret that Apple targets the higher-end of any market they enter, promoting their superior platform, product and support. So I would expect the Tablet to retail at a higher price point than other comparative products (namely Windows based Tablet-Netbooks) which sell for AUD $700 upwards. The question I’d love answered is “will the masses buy theTablet”? At an estimated AUD $1000+ it’s a steep price to ask for a device which isn’t as portable as the iPhone or as powerful and flexible as your standard laptops/desktops.
Rumours generally agree that the Tablet will run a form of the iPhone OS, and that it will have access to the App Store and other Apple related goodies (iTunes, and its movie rentals etc). This is important as it instantly means the tablet will be less suited for actual work, and more geared for casual use and entertainment. Just imagine it as being a device you’d have around your home, something that you could use to read the news, watch YouTube videos, and stream movies to. Who knows, Apple may even surprise us all with Infra-Red support, turning the Tablet into the ultimate lounge room remote control. Or maybe they’ll include Augmented Reality, where an embedded camera can identify real world objects and bring up helpful information about it (eg. Show it a TV channel and it would tell you what’s on next, or offer you ways to download the show for later viewing).
This still brings us back to the question… is it worth the estimated $1000 price tag? It leaves me feeing squeamish at the thought of forking out a grand for a device that is less useful than a computer, and will probably just end up sitting around the house all day (unlike the highly portable iPhone which you’d carry everywhere with you). It’s a strange new territory that Apple will be stepping into. Until the 27th of January when it will be officially released in San Francisco, it’s anyone’s guess how things will turn out. Either way, the iSheep will be out in full force throwing their support behind any new Apple product come rain or shine.
How Google Wave can improve your Business
11th Oct 09
I’m guessing most of the world has heard a little above Google’s upcoming product and service, Google Wave. It brings a new way of collaborating, communicating and sharing information between friends, colleagues, and the public. Just recently Google has been handing out over 100,000 invites into the preview program. As you could imagine this has generated a fair bit of buzz on Twitter and the Blogosphere over the last few weeks. Even though Wave is still very much in its infancy, I’ve been considering how Google Wave could benefit small businesses through to enterprises and what advantages it would bring over existing Enterprise 2.0 tools (specifically email, instant messaging, wiki’s, and blogs).
For those unfamiliar with Google Wave I would suggest taking a look at my previous article introducing Google Wave, or if you’re after more detail have a read of this comprehensive run-down on Google Wave by Orielly. From here on I’m going to focus on comparing existing business productivity tools one by one against Wave to tease out their respective disadvantages or advantages.
Email
Email has been around for ages. It has served a vital role on the business frontline for the last 10+ years and is well established and supported. Originally email adoption was largely a product of internet adoption, but now days a large percentage of Australians (and the world) have access to the internet not only at home, but also on the go. Unfortunately Email also brought some new challenges, including SPAM and the increasing complexity and length of emails as a conversation grows. Additionally email conversations can easily splinter away into distributed private conversations, potentially preventing important information from being shared with the rest of the company. As Bill French said “E-mail is where knowledge goes to die”. Google Wave attempts to solve this by keeping the knowledge in a single location, so it’s much harder for information to be spread everywhere (and lost). As with all Google products you’ll be able to use its leading search engine to find information or conversations later on down the track.
You can also leave comments at the exact position in the document you are referring to. The “regarding your question in paragraph 3” scenarios that commonly occur in emails will soon be a relic of the past, keeping conversations better organized as they grow in size. There’s also private messaging within Wave should you need to share something with select individuals rather than the whole group (similar to BCC in emails). Again, these private conversations are kept within the Wave, making it easier for you to find everything in the future.
The major advantage I can see of email over Google Wave is the sheer scale of adoption worldwide. Also, Email is better suited towards static read-only content such as email newsletters or other simple once-off emails (Invoices, Password Reminders etc). Where Google Wave shines is in conversation or collaborative scenarios. For example Wave would excel in Issue Tracking (eg. IT Help Desk), Research, Project Collaboration, and any other situation where more than one email would normally be necessary.
Wiki’s
Wiki’s can benefit enterprises through their ability to accurately capture, store and share knowledge by allowing individuals to collaborate together on shared documents. Wiki’s can track the changes made to documents over time, however they lack Google Wave’s elegant playback feature. Like Wave you can collaborate in near real time and you’ve got user access controls at hand if you need restrict access to sensitive information. The disadvantage of Google Wave is that it’s inherently conversational, making linking pieces of information together slightly awkward. So for large scale uses you would be better off sticking to Wikimedia or other dedicated Wiki tool.
What I can imagine is integration between Wiki’s and Wave. Imagine using Google Wave to subscribe to a wiki page you wish to edit. A quick playback of the page’s history would bring you up to speed on the conversation between contributors and the latest version of the document. From there you could make your own changes to the wiki and chat with others, all inside Wave. A Wave Robot would then post your changes back to the wiki, automatically keeping both Wave and the Wiki in sync. Potentially the robot could even bring across your comments too so that others without Wave can still benefit from the conversation.
Instant Messaging
Cause of its real-time conversation abilities, Google Wave lends itself quite nicely to instant messaging (IM). In fact it does one better because you can see what the other people are writing before they even finish their message. This allows you to gather your thoughts and even start working on a reply before they are finished. This can save some serious time versus the traditional IM way. Once everyone has finished the conversation it’s automatically saved for future reference. Anyone else with access to it can play it back and even continue the conversation if they wanted. All the other individuals will be notified of any continuations of the conversation. The conversation is also indexed, so you can use the search feature to quickly find old conversations. Also instead using two tools (a Wiki and an IM client for example) individuals can simply use Wave to get everything done, and everything gets stored in the same place. The only advantage to IM over Google Wave is that clients are usually much simpler to use, and are available even on basic mobile devices.
Blogging
Google Wave and Blogging are distinctly different in purpose and intent. Blogging is a static publishing medium, whereas Wave is more a collaborative tool. However Wave does have the potential to influence blogging and publishing in general. Instead of a single source posting an article, imagine hundreds of users all contributing to the latest story on a public Wave. Photos could be uploaded in real-time as events unfold. Kind of similar to Twitter, but stories could be better filtered, grouped and moderated (like Wiki’s). Google have also demonstrated Wave integrating with blogging platforms using its embed API. So it’s likely that Wave will complement blogging rather than replace it.
Effects on Business?
Google Wave is made up of three pieces: the Wave Client, Wave API’s and the Wave Federation Protocol. The exciting stuff for businesses will most likely happen in the Wave API’s and/or Federation Protocol. This is where businesses can integrate Wave with their existing business software and services, something SAP have already demonstrated. It will be interesting to see if Wave’s open platform will encourage adoption among business.
Another major advantage of having an open platform is that businesses can run their own Wave servers, keeping company secrets within their own IT infrastructure. It also means they can customise their Wave clients to integrate nicely into their Intranet environment. Also being a web application the costs of ownership are low because everything runs in a web browser and uses standard HTTP ports to communicate which negates the need to rework existing firewalls or security infrastructure.
Wrapping it Up
Google Wave can really make business more efficient through its superior knowledge management, real-time collaboration, and by having the ability to share rich media in Waves. Businesses can also build their own Wave clients or Robots to integrate with their existing infrastructure and services. Better yet, we might even seen vendors releasing free Extensions for Wave as a way of building value in their current products. Businesses also have the option of hosting their own Waves servers in order to control availability and security while having a degree in freedom in customizing the service.
As promising as Google Wave is on paper we’ll still probably see the same adoption rates that many other Enterprise 2.0 and Web 2.0 efforts have encountered. Like past efforts, it’s likely that clusters of employees or project teams will drive bottom-up adoption of Wave, with few top-down strategies being introduced. I really hope that managers and CEO’s can comprehend the value that Google Wave could bring to their business in terms of productivity increases and improved knowledge management. I think the low initial adoption costs would easily be regained many times over.
It’s not me, it’s you
9th Sep 09
In reply to the video that Brett introduced on his blog… (post here)
The Machine is Us/ing Us – YouTube
After reflecting on that video I think Web 2.0′s mantra should be “It’s not me, but you” (nothing to do with Lily Allen if you’re wondering). The thing that makes Web 2.0 so useful and engaging is that it’s foundations are on people sharing and collaborating. In fact Web 2.0 is merely a framework for harnessing global knowledge and talent. Without people it would be largely regarded as a failure.
Web 2.0 was made possible through broadband reaching the masses. I honestly couldn’t imagine YouTube, Facebook, Flikr, or even Wikipedia working on 56k dialup. While web 2.0 featherweight Twitter could have worked, it wasn’t until 5-7 years ago that a good percentage of households had an internet connection full stop. Besides, without its predecessors Instant Messaging, Blogging and SMS, I don’t think it would have been as popular had it been released 10 years ago. In fact I’d go out on a limb and say that most people wouldn’t have understood it back then.
It’s interesting that the Australia government is pushing for the National Broadband Network (NBN) which promises a brand new Fibre to the Home (FTTH) network running at speeds of up to 100Mbit. The government’s vision is to build the new network ahead of its time in order to establish Australia as a leader in next-generation technologies and applications. At CeBIT in Sydney this year I was listening to industry analyst Paul Budde speak on topics related to the NBN. One of the points he raised was that developers need to start creating applications for the new network in order to create some value in it. Right now most Australians are happy with their 1Mbit+ speeds, so there’s no need or desire for the newer, faster network… that is until new applications appear. Kind of a chicken and egg scenario.
Should the network eventuate it could present some great opportunities for Web 2.0 and Enterprise 2.0 applications in Australia. Right now most people have access to broadband connections either at home, work, or on their mobile phones. We’ve also seen Web 2.0 applications explode in popularity over the last few years and there are no signs that growth could be slowing anytime soon. And with the NBN on the horizon, the stage is set for the next generation of web applications to arrive.





Recently I took the plunge and signed up to Twitter, the hugely popular micro-blogging site. Even though I had known about Twitter for roughly 2 years, and even used it for other purposes I thought I was time to sign up with my own account 