What on Earth is RSS Cloud?

Arjen Vrielink and I write a monthly series titled: Parallax. We both agree on a title for the post and on some other arbitrary restrictions to induce our creative process. For this post we agreed to write about a new technology using Linux Format‘s “What on Earth is …?” style (see example on Android). We did not agree on a particular technology and we would get bonus points for a nice pixellated image to accompany the post. You can read Arjen’s post with the same title here.

RSS Cloud
RSS Cloud

RSS Cloud? I am getting a bit tired of this cloud computing trend.
Yes, I also think that cloud computing is slightly over hyped. However RSS Cloud is not about cloud computing. It is about bringing real-time updates to the RSS protocol.

I have only just grasped what RSS is. Only the technorati seem to use it, normal computer users have no idea.
Indeed: most people have no idea what RSS is or how they can use it. They still visit all their favourite news sites one after the other to check whether something new has been posted. However even people that don’t understand it often use it. If you download podcasts through iTunes you are using RSS technology. Furthermore RSS is the technological glue for many of the popular mashup sites. You don’t need to understand a technology for it to be useful to you.

Fair enough, so how would you explain RSS Cloud to a lay person?
Sites that have content that changes often (think blogs or news sites) publish an RSS feed on their server. Whenever a new item is posted it will be added to the feed, usually dropping the oldest item from the list at the same time. If you are interested in those news items you can use a news reader (also called an aggregator) and tell this news reader to check whether new items are added to the feed, if there is an update, then the news reader can retrieve it. A news reader typically does this every fifteen minutes or so. This means the news can be 15 minutes old when you get it. RSS Cloud makes it possible for news readers to subscribe to the updates of a feed. Whenever something new is added the feed, the RSS Cloud server notifies all subscribers so that they can pick up the content immediately: in real-time.

Another buzz word! What is the benefit of real-time? Can’t people just wait a couple of minutes before they get their news?
People listen to the radio so that they can hear the sports results in real-time. Weren’t you upset when all your friends knew about Michael Jackson’s death earlier than you, because they heard it on Twitter? The success of Twitter search and trending topics shows that people want to know about stuff as it happens and not fifteen minutes later.

Now that you mention it: Twitter indeed works in real-time. Why do we need something else, what’s wrong with Twitter?
Twitter actually also uses a “polling” model for its content. Each single Twitter client will have to access the Twitter API to see whether something new has been posted by the people you are following. This is a huge waste of computer resources. All these clients asking for new information even if there is none. It is a model that does not scale well. A “push” model actually works much better in this respect.

Oh, so it is a bit like the difference between getting your email once every couple of minutes and getting it immediately on your Blackberry?
Yes, that is a nice analogy. The Blackberry uses push email. You get the email as soon as it hits the server, because it is pushed to your phone. Traditional email clients, like Outlook, go to the server once every couple of minutes to see whether something new is there.

So what large company is trying to push this idea?
This time it is not a big company trying to establish a standard or protocol. The RSS Cloud protocol is designed by Dave Winer who also drafted the original RSS specification.

Dave Winer, isn’t that the guy that loves to rub people the wrong way?
He is a controversial character and is certainly very vocal and opinionated. At the same time, he is a true pioneer and one of those people that embody the values of the Internet. His vision for Cloud RSS is not about blogging. Instead, he wants to provide a decentralised architecture for microblog messages. To him the fact that Twitter centralises all the microblogging activity is a real vulnerability. His goal is to create a network that can work alongside Twitter without being in the control of a single company.

Talking about companies. I suddenly remember hearing about a similar technology. One of these cute names with many vowels?
You probably mean PubSubHubbub. This is a Google sponsored protocol that has already been implemented in Google Reader.

Great: another standards war. VHS versus Betamax, RSS versus Atom, Britney versus Whitney. Will we never learn?
This shouldn’t become a problem. RSS and Atom for example live happily next to each other now. It is easy to implement both. PubSubHubbub has a slightly different goal in comparison to Cloud RSS. It focuses mainly on blogging and associates itself with Feed Burner. The two technologies should be able to live next to each other, at least that is what Dave says.

Well, let’s hope he and you are right. By the way, isn’t this Cloud RSS just another sneaky way to measure subscribers, generate some statistics and store information about where they are from and what they are doing?
It is true that an RSS reader will have to register itself with the the RSS cloud for the protocol to work. However the RSS cloud forgets about the RSS reader if the registration isn’t renewed every 24 hours. You also have to remember that many people will use readers that do not support RSS Cloud. There are much better ways to get statistics.

Aren’t you a learning technology person? What does this have to do with learning?
I am very interested in Cloud RSS because I am a learning technologist! Like all new Internet based technologies it will only be a matter of time before some smart developer finds a way of using this in some unexpected fashion. Remember:
technology creates feasibility spaces for social practice! Just think of what kind of course delivery models RSS has made possible: the Connectivism and Connective Knowledge course could not run without it for example.

You are a Moodle evangelist. Does Moodle support RSS Cloud yet?
I haven’t checked, but I doubt it.  It is very new and the Moodle developers are focusing on getting Moodle 2.0 to a beta release. However, I am sure that in the future, parts of Moodle will move towards real-time. Imagine how Cloud RSS could be used to create activity streams or notify people of comments on their work. It could effectively bridge the gap between asynchronous activities like discussion forums and assignments and synchronous activities like web conferencing.

Ok, you have managed to pique my interested. Where can I go if I want to start using it?
There are two ways of using it. First, you can make your own feeds RSS Cloud enabled. If you have blog at WordPress.com this is automatically the case. You can opt-in if you host your own WordPress blog. The other way of using it would be to have an RSS reader that supports the protocol. Currently only River2 supports it and Lazyfeed has announced that it will support it too. Only web based readers can support it, as the RSS Cloud server needs to be able to ping the reader with the update.

Are there any sites that can tell me a bit more?
The current home of the protocol is http://www.rsscloud.org. Here you will find news about the protocol and an implementation guide. The Wikipedia entry could be better. Why don’t you help fixing it?

Why Chromium is Now My Primary Browser

Arjen Vrielink and I write a monthly series titled: Parallax. We both agree on a title for the post and on some other arbitrary restrictions to induce our creative process. For this post we agreed to include our personal browser histories in the post. You can read Arjen’s post with the same title here.

Chromium Logo
Chromium Logo

If you are not interested in Browsers and/or usability, I would suggest you don’t bother to read this post.

I cannot exactly remember the first time I used the Internet. It probably was in 1996 in the library at the Universiteit Utrecht. I wasn’t particularly aware of the browser I was using, but I am quite sure that is was Netscape Navigator with which I did the Altavista searches. I used Netscape throughout my education, only to switch to Internet Explorer 5 when I got my own computer with Windows 98 and a dial-up Internet connection. I then used nothing but IE until I read about Mozilla Firefox in a magazine in 2004. Through Moodle I had started appreciating open source software and I liked working with Firefox and its tabs. I stuck with Firefox for a year or so, feeling quite the rebel whenever a site would only load in IE. At some point I noticed how much faster IE was than Firefox. That is when I switched to Avant Browser, a freeware skin around the IE browser engine which included tabs and some other advanced features. A little while later (somewhere in late 2005 or early 2006) I learnt about Opera. Opera had a lot of appeal to me. I liked how their developers pushed so many innovations in the browser space: tabbed browsing, advanced security features and mouse gestures were all inventions of Opera. I loved how fast it was and how many features they managed to cram in so little megabytes. Its cross platform nature allowed me to stay with Opera when I permanently switched to Ubuntu in the summer of 2006. I switched back to Firefox in early 2007 because of my slightly more hardcore open source attitude and because of its wonderful extensions. The latter allowed me to keep all the functionality that I loved about Opera and more.

About two weeks ago I switched to Chromium. This is Google’s relatively new open source offering in the browser market. I am able to automatically download new builds every day through the PPA for Ubuntu Chromium Daily Builds. Even though it is still beta alpha software, it is highly usable.

So why did I switch? I think there are three reasons:

1. Performance
Since a couple of months my private computing is done with a Samsung NC10. This Intel Atom based netbook is slightly underpowered. You really notice this when you are doing things like recoding a video or doing some CPU intensive image editing. I also noticed it terribly in Firefox. Things like Google Reader, DabbleDB (watch that 8 minute demo!) and the WordPress admin interface were nearly unusable. A cold start of Firefox (the 2.x version that comes with Ubuntu 9.04) takes nearly a minute. Chromium on the other hand starts up in a couple of seconds and is very spiffy with Javascript-heavy web-apps.

I tried to quantify my unmistakable feelings with some benchmarking. I used Peacekeeper, but Firefox could not finish the benchmark and would crash! I then used the Sunspider Javascript benchmark and got a total score of 3488.8ms for Chromium and a total score of 18809.6ms for Firefox. This means that in certain cases Chromium would load something in less than one fifth of the time that Firefox 2.x will load it.

While writing this post I decided to try installing Firefox 3.5 (without add-ons) and see how that would perform. After a sudo apt-get install firefox-3.5 I could start Firefox by selecting “Shiretoko Web Browser” in the “Internet” menu. The total score was 5781.2ms, a major improvement, but still more than one and half times slower than Chromium. Its interface is also still less responsive than I would like it to be.

Another nice aspect about Chromium’s performance is that each tab is its own process. This so called Multi Process Architecture isolates problem webpages so that one Flash page crashing does not affect the other browser tabs, something that happened very often to me with Firefox.

2. Screen Real Estate
Another thing that a netbook lacks is pixels. My screen is 1024 pixels wide and 600 pixels high. Especially the lack of height is sometimes taxing. I have done a lot of things in Ubuntu to mitigate this problem (if you are interested I could write a post about that) and I had to do the same with Firefox.

In Firefox I used Tiny Menu, chose small icons, used no bookmarks and combined many toolbars into one to make sure that I have more content and less browser. To my surprise I had to do nothing with Chromium and still got a bigger canvas with a bigger font in the address bar! Compare the screenshots below to see the differences: 

 

Screenshot Firefox (click to enlarge)
Screenshot Firefox (click to enlarge)
Screenshot Chromium (click to enlarge)
Screenshot Chromium (click to enlarge)

 

Chromium shows more of the page and accomplishes this by doing a couple of smart things:

  • There is no status bar. I could have turned the status bar off in Firefox, but I need to see where a link is pointing to before I click on it. Chromium shows this information dynamically as soon as you hover over a link. When you don’t hover it shows nothing.
  • The tabs are moved into the title bar. It looks a bit weird for a while, but it uses some very valuable space.
  • Some things only appear when you need them. The bookmark bar, for example, only shows up when you open a new tab.

3. It is a fresh look at what a browser should/could be
Most of my time behind my computer is spent using a browser. More and more of the applications I use daily have moved into the cloud (e.g. mail and RSS reading). It is thus important to have a browser that is made to do exactly those functions.

The developers of Chromium have looked at all aspects of a traditional browser and have rethought how they work. A couple of examples:

  • The address bar is actually a tool with four functions. It contains your web history, typing some terms will execute a search in your default search engine (saving me two characters compared to how I search in Firefox), you can type a normal web address and you can use keywords to search. If I type w chromium in the address bar it will search for chromium in Wikipedia. The keyword search also works in Firefox, but Chromium has a prettier and more clear implementation.
  • When you open a new tab, you see a Dashboard of sites you use often (a variant of another Opera invention). That page also conveniently displays recently closed tabs with a link to your browsing history. The history page has excellent search (it is Google after all!) and has that simple Google look.
  • The downloads work in a particular way. They automatically save in a default location unless you tick a box confirming that you always like to open that type of file from now on. This takes a little getting used to (I like saving my downloads in different folders), but once again the download history is searchable and looks clean.

In conclusion: Chromium is a browser in which some hard choices were made. No compromises. That means that I, as a user, have to worry about less choices and settings and can focus on being more productive. Making tough interface design choices can be a very successful strategy: witness Apple’s iPod.

For now I will be using Chromium as my primary browser and will use Firefox when I need certain functionalities that only Firefox add-ons can provide.

I am looking forward to what the browser future holds!