In my previous post I mentioned aggregate readers tied to RSS feeds as a key component of harnessing collective intelligence in the Web 2.0 age. I also promised that, sometime in the future, I would write a post on aggregate readers, and I still intend to do that. However, this morning while surfing some older Google blog entries I came across an interesting post on using Google Reader with the Nintendo Wii gaming system. As a Google Reader fan, and new Wii system owner (Christmas) I was intrigued by this combination.
Before getting started, however, it's important to note that in order to use Google Reader with the Wii, your Wii must be connected to the net (I know that's a blinding flash of the obvious, but I thought I better float that small detail out there...). The other thing you're going to need is the Opera-based browser for the Wii, which can be purchased for a few dollars (Wii Points) through the Wii Shop Channel. Once you have this, you're all set. Fire up the browser on your Wii and navigate to google.reader.com. If you'd like to try the Google Reader interface in a regular browser, visit www.google.com/reader/wii to go into Wii mode.
The Opera browser is a little clunky -- you have to be patient entering URLs -- and navigating with the Wii remote can test your patience, but it was nice to sit in my Eames Lounge Chair and check out the updates that were flowing in to my Google Reader. It's not as efficient as a traditional browser, but it's better than what you get on a hand-held device such as a Blackberry. Below are the simple navigating instructions for using the Wii remote.
up/down: scroll up/down
right/left: next/previous item
1 button: show subscriptions
2 button: show links
When showing subscriptions:
up/down: previous/next subscription
right: select current subscription
left: close
-/+: collapse/expand folder
All things considered, I found the Google Reader on the Wii to be a good option if you're too lazy on a rainy Sunday morning to get your laptop.
If your interested in some more detail, check out Mihai Parparita's blog post. Also, check out the below video, which was also included as part of Parparita's post. Enjoy.
The second of Tim O'Reilly's seven Web 2.0 principles is Harnessing Collective Intelligence [1]. Harnessing collective intelligence means that individuals surfing the the web have the ability to add and/or modify the content of a web page -- thus adding collective intelligence. I have found three key examples that explain this principle nicely.
The prime example associated with this principle is Wikipedia. If you don't already know, Wikipedia is an online encyclopedia that allows any web user to create or edit entries -- as opposed to, say, Encyclopedia Britannica, which uses a relatively small number of experts to derive their information from. Wikipedia offers a wide-open social forum that encourages participation, but also has an established methodology for ensuring the veracity of the information contained within the site. Some argue that allowing the free-form creation and editing of information is dangerous business, and that the information offered by the Wikipedia nation is not reliable. However, according to a 2005 study conducted by the journal Nature, Wikipedia is every bit as accurate as Encyclopedia Britannica[2]. The Wikipedia model for a user-created encyclopedia, to many, is a monumental leap of faith. O'Reilly refers to it as a "radical experiment in trust" [1]. However, the Wikipedia idea has been successful enough that it has become the model for a new U.S. intelligence community collaboration initiative called Intellipedia. And the term wiki has become synonymous with collaborative web sites. For more information on Intellepedia see Clive Thompson's New York Times article titled, "Open-Source Spying" [3].
Another key example of Harnessing Collective Intelligence is the rise of the blog. Personal web pages have been around since Al Gore created the Internet. However, the current format of "personal pages" -- the blog -- allows the common web surfer (like yours truly), with no knowledge of HTML, to create highly interactive, chronological running dialogues with rich content. Like a wiki, a blog offers web surfers a myriad means to create, edit, and control information. This blog is a good example because, with very little training, a casual computer user like me can create an interactive site that hosts hyperlinks, pictures, streaming video, and the ability for site visitors to comment on the blog content.
A technology called Really Simple Syndication/Rich Site Summary (RSS) is another important tool for harnessing collective intelligence. If you spend any time surfing the web, chances are you have seen the icon located to the left. O'Reilly goes so far as to categorize that "RSS is the most significant advance in the fundamental architecture of the web since early hackers realized that CGI could be used to create data-based backed websites" [1]. In its simplest form RSS allows a web surfer to subscribe to a page, and receive notification every time the content on that page changes. The link between RSS, the wiki, and the blog is the fact that RSS has created an ease of interaction between all of the Web 2.0 collaboration tools. RSS "pushes" information to a single location (the aggregator), which in turn increases the interaction on wikis and blogs.
In order to view RSS feeds you need to have what's called an aggregator. An aggregator provides a consolidated view of content in a single browser display or desktop application. There are a number of web and client-based aggregators available as freeware. I will discuss aggregators in a future blog, but for those not familiar with them, Google Reader is a great web-based aggregator, while FeedReader offers a solid client-based aggregator. More to follow on this subject...
Finally, Michael Wesch, Assistant Professor of Cultural Anthropology at Kansas State University, released the below video titled "Web 2.0 ... The Machine is Us/ing Us" on YouTube on January 31, 2007. The video sums up nicely some of the things I have discussed in this blog entry.
Allowing users to create and edit data is a profound advancement in the evolution of the internet. Wikis, blogs, and RSS are but a few key examples of how the web community collaborates and endeavors to harness a collective intelligence.
In the previous post I described the simple differences between Web 2.0 and Web 1.0 and identified seven principles outlined by Tim O'Reilly [1]. O'Reilly's seven principles offer a logical jump-off point for exploring the Web 2.0 phenomenon. In this entry I will discuss his first principle, The Web as Platform [1].
According to O'Reilly, "You can visualize Web 2.0 as a set of principles and practices that tie together a veritable solar system of sites that demonstrate some or all of those principles, at a varying distance from that core" [1]. See the below "meme map" for a graphical description. The map offers an outstanding visual -- a picture is worth a thousand words -- for how Web 2.0 is developing the web as platform. Most importantly, the web (the platform) is constantly changing to meet the needs of the Internet community -- giving the user a stake in the development and modification of content accessible to any user with a browser and web access.
One of the key ideas of The Web as Platform is that client side applications, such as the Microsoft Office Suite, and their development, release, and distribution cycles will become obsolete. O'Reilly sums this philosophy up nicely [1]:
"There will be no scheduled software releases, just continuous improvement. No licensing or sale, just usage. No porting to different platforms so that customers can run the software on their own equipment, just a massively scalable collection of commodity PCs running open source operting systems plus homegrown applications and utilities that no one outside the company ever gets to see."
The Web as Platform is a key principle to understanding the Web 2.0 phenomenon. The ability to harness collective intelligence to create and edit data collectively within the web community is what makes the web a powerful, scalable platform. The Web as Platform principle allows users to run software applications entirely through a browser. Instead of just viewing a site, Web 2.0 sites often offer rich, user-friendly interfaces that encourage users to add value to applications as they use them.
In the next blog entry I'll discuss the second principle: Harnessing Collective Intelligence.
According to Wikipedia, Web 2.0 is "a second generation of web-based communities and hosted services such as social-networking sites, wikis, blogs, and folksonomies, which aim to facilitate creativity, collaboration, and sharing among users." This differs from the so-called Web 1.0 technologies, which were static and did not allow interaction and collaboration. Tim O'Reilly of O'Reilly Media, and Dale Dougherty of MediaLive International, co-creators of the "Web 2.0 Conference," offer the below examples of the differences between Web 1.0 and Web 2.0 technology.
Web 1.0
Web 2.0
DoubleClick
>
GoogleAdsense
Ofoto
>
Flickr
Akamai
>
BitTorrent
mp3.com
>
Napster
Britannica Online
>
Wikipedia
personal websites
>
blogging
evite
>
upcoming.org and EVDB
domain name speculation
>
search engine optimization
page views
>
cost per click
screen scraping
>
web services
publishing
>
participation
content mgmt systems
>
wikis
directories (taxonomy)
>
tagging ("folksonomy")
stickiness
>
syndication
Additionally, O'Reilly, writing a 2005 article titled "What is Web 2.0," explored seven principal features (1. The Web as Platform; 2. Harnessing Collective Intelligence; 3. Data as the Next Intel Inside; 4. End of the Software Release Cycle; 5. Lightweight Programming Models; 6. Software Above the Level of a Single Device; and 7. Rich User Experiences) that he considers core competencies of Web 2.0. Upon initial research, O'Reilly's seven principles appear to be a logical organization for exploring Web 2.0.
Recently I attended a class called "Social Software 101." The class was designed to initiate professionals into the Web 2.0 revolution. That's real nice, but what is the Web 2.0 revolution? What I found is that many of the so-called Web 2.0 tools are used by the casual computer user - which I categorize myself - every day. We just don't know it. The class really peaked my interest and I have been doing a lot of reading to attempt to understand the Web 2.0 phenomena. In my reading I have found that the information available on Web 2.0 is overwhelming. But what I have not found is that one web stop that breaks Web 2.0 down for newbies - or the casual web surfer like myself. What I hope to do with this blog is twofold: 1) Better understand the Web 2.0 phenomena; and 2) Translate my learning into a running dialog for other Web 2.0 newbies.
